Re: [boost] Bug in iterator_range when NDEBUG not defined but boost asserts are enabled

From: David Abrahams (dave_at_[hidden])
Date: 2008-05-13 09:00:23

on Tue May 13 2008, Thorsten Ottosen <thorsten.ottosen-AT-dezide.com> wrote:

> John Reid skrev:
>> iterator_range.hpp defines is_singular() if NDEBUG is not defined but it 
>> calls is_singular through the BOOST_ASSERT macro. Unfortunately it is 
>> possible to enable BOOST_ASSERT and have NDEBUG defined which leads to a 
>> compilation error.
>> 
>> To see this compile the iterator_range.cpp example included with the 
>> library with the following defines:
>> gcc -DBOOST_ENABLE_ASSERT_HANDLER -I/usr/local/src/boost-trunk/ -DNDEBUG 
>> -c iterator_range.cpp
>
> I'll look into this when I get some time. I guess most people write 
> assertions under the implicit assumption that they are either on or off.

I dunno.  IIUC part of the motivation for BOOST_ASSERT was to have
something that would be tested even when NDEBUG was defined.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com