Re: [Lilypond-auto] Issue 2787 in lilypond: Sanitize usage of -DDEBUG, -DNDEBUG, assert, programming_error and so on

[lilypond]

Updates:
        Status: Started
        Owner: address@hidden
        Labels: Patch-new

Comment #1 on issue 2787 by address@hidden: Sanitize usage of -DDEBUG,  
-DNDEBUG, assert, programming_error and so on
https://code.google.com/p/lilypond/issues/detail?id=2787#c1

Issue 2787: Sanitize usage of -DDEBUG, -DNDEBUG and assert

The compiler option -DNDEBUG is no longer being used: -DNDEBUG disables
the assert function, and assert is essentially stating that the program
cannot useful continue if the assertion is not met.  -DNDEBUG is
basically an option for compiling an application to a limited amount of
ROM when aborting with a diagnostic is not preferable to crashing.

This is not the case for LilyPond.  So expensive debugging options now
are enabled with -DDEBUG instead.  At the current point of time, setting
this is still tied to the configure option --disable-optimising.  It
might make sense to move this to a separate option --enable-testing or
similar, but that would require simultaneous changes to the Patchy
testing framework.

http://codereview.appspot.com/236190043

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings