Leo Sutic wrote: > > Berin, > > great idea. I have some minor comments, though. > > > -----Original Message----- > > From: Berin Loritsch [mailto:[EMAIL PROTECTED] > > > > 'all' > > Compiles the program with debugging enabled by default. > > This target is not required to build documentation. Standard > > compilation properties and defaults are: > > * build.debug=on > > * build.optimize=off > > I think this should be: > > * build.debug=off > * build.optimize=on > > If we're targetting those who just download + install stuff without any > intention of developing, there is no need for debug information, but need > for optimization.
Yes and no. The GNU make docs made a good point on this. These are build parameters so they can be overridden. By building with debug information by default, we can get more information from stack traces. When people send in pub reports with stacktraces where debug information is stripped, we have no line numbers making the bug harder to fix. Optimization sometimes makes it impossible for the JRE to give line numbers in certain situations, but I am open to turning it on once there is a release to be made. During development, optimization should be off and debug should be on. During release, debug should be on and optimization can be turned on. If a user turns off debug information, then it must be assumed that they know what they are doing. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
