
7 Apr
2009
7 Apr
'09
8:19 p.m.
Hi All, #define BOOST_DISABLE_ASSERTS #include <boost/assert.hpp> #include <call.h> int main(){ call(); return 0; }; If, for testing purposes, I define call() as BOOST_ASSERT(false); with or without -O2 as a compiler option, there are no assert failed messages during execution, as desired. In my actual program, however, call depends on many headers. If I artificially add BOOST_ASSERT(false); in one of them, it is not ignored with -O2 i.e. I get Assertion failed: (false), function call. I use i686-apple-darwin9-gcc-4.0.1. Am I using BOOST_DISABLE_ASSERTS correctly? How do I go about fixing this problem?