Updates:
Status: Fixed
Labels: -Patch-push -Type-Scripts Fixed_2_19_21 Type-Build
Comment #8 on issue 2787 by [email protected]: Sanitize usage of -DDEBUG,
-DNDEBUG, assert, programming_error and so on
https://code.google.com/p/lilypond/issues/detail?id=2787
Pushed to staging as
commit a4cc910a3401d25bb94ff0ecb4dc18f681c71004
Author: David Kastrup <[email protected]>
Date: Tue May 12 19:01:57 2015 +0200
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. There is a new configure option
--enable-checking defaulting to "off" for this now.
At the current point of time, setting --disable-optimising also has the
effect of enabling the checks: this will be retained until Patchy has
been adapted to using --enable-checking.
--
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
