From: Peter Dimov (pdimov_at_[hidden])
Date: 2005-09-21 13:29:50
Dave Harris wrote:
> I did not use NDEBUG because BOOST_ASSERT doesn't, and I didn't want
> to revisit that decision. I imagine the policy is to use fine-grained
> flags and then add:
> #ifdef NDEBUG
> #define BOOST_DISABLE_ASSERTS
> in a user-editable header somewhere.
The default behavior of BOOST_ASSERT is to expand to 'assert'. This means
that it obeys NDEBUG, as usual.
BOOST_DISABLE_ASSERTS is for situations where the user needs to disable all
BOOST_ASSERTs (no assertions from within Boost are desirable) but all plain
'assert's are to be left alone.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk