Peter Lundblad wrote:
> the current situation regarding --enable-debug and
> --enable-maintainer-mode is a little confusing.
> --enable-debug enables compiler debugging, but not the SVN_DEBUG and
> AP_DEBUG macros. OTOH, --enable-maintainer-mode does the latter,
> but does not enable compiler debugging, although it pretends to do
> so by setting an internal variable, but too late... Uh...
> I'm not sure if we need two options here, but it might be good to
> leave --enable-debug to not cause problems for people with automated
> builds. Also, --disable-debug can be used to disable debugging
> Anyway, any objections to this patch that tries to make this a little
> less confusing?
While we're here, is there any reason why --enable-maintainer-mode doesn't
turn off compiler optimization? Seems unnecessarily difficult to "maintain"
code that's nearly impossible to step through in a debugger.
C. Michael Pilato <firstname.lastname@example.org>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Fri Mar 23 03:17:34 2007