On Mon, Mar 9, 2009 at 9:41 AM, Tim Kroeger <tim.kroe...@cevis.uni-bremen.de> wrote: > On Mon, 9 Mar 2009, John Peterson wrote: > >> On Mon, Mar 9, 2009 at 9:23 AM, Tim Kroeger >> <tim.kroe...@cevis.uni-bremen.de> wrote: >>> >>> (Feature-request: Use LIBMESH_DEBUG rather >>> than DEBUG.) >> >> This would probably be ok... since assert's happen when NDEBUG is >> *not* defined if I remember correctly, and don't care about DEBUG. >> Can anyone else comment? > > You're right; I found it in libmesh_common.h, line 218.
Yes, with libmesh_assert, we wanted to mimic the behavior of stdlib's assert. > But what does that help me? Is there a configure option that results in > neither defining DEBUG nor NDEBUG? Our did you mean that asserts are always > enabled unless I manually define NDEBUG? In optimized mode you get -DNDEBUG, in debug mode you get -DDEBUG, and in devel-mode you get neither. I was just making the statement that we probably wouldn't affect other standard library functions by changing DEBUG to LIBMESH_DEBUG. We might break something by changing NDEBUG to LIBMESH_NDEBUG, I also realize this is not what you are proposing. > In any case, I would like to hold my feature request up. It sounds reasonable to me, unless -DDEBUG is required by other standard library functions, which I don't think it is... -- John ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
