Re: [boost] Re: Filesystem test fixes for OS X release mode

From: Beman Dawes (bdawes_at_[hidden])
Date: 2005-01-16 12:08:08

At 09:52 AM 1/16/2005, troy d. straszheim wrote:
 >Beman Dawes wrote:
 >> At 05:46 PM 1/15/2005, Rene Rivera wrote:
 >>  >Would a temporary "#undef NDEBUG" in Boost.Config, activated only 
while
 >>  >testing, work?
 >>
 >> It is possible there may be cases where the #undef NDEBUG should only
 >> apply to <cassert>. So it might be better if it were given explicitly 
in
 >> the test program.
 >
 >Might the most straightforward thing be for test modules to have their
 >own NDEBUG-ignorant assert macro?  The vast majority of the work could
 >just get done with a perl one-liner.  I would expect people to forget to
 >add the #undef NDEBUG, and then you just get more tests creeping in that
 >don't do anything.

This whole discussion may be a bit of a red herring. I wonder how many 
Boost libraries still depend on assert for testing (as distinct from 
asserts in compiled libraries)? Many use Boost.Test.

--Beman