From: Beman Dawes (bdawes_at_[hidden])
Date: 2004-10-11 19:09:08
At 06:35 PM 10/11/2004, you wrote:
>> > No. It is undefined behavior for boost::throw_exception() to return.
>> > To quote the throw_exception() docs:
>> > Callers of throw_exception are allowed to assume that the
>> > function never returns; therefore, if the user-defined
>> > throw_exception returns, the behavior is undefined.
>> It is definitely not a bug. However you might want to consider - purely
>> QoI issue, of course - to return 'false' instead of 'true' when
>> throw_exception returns. ;-)
>> Unsubscribe & other changes:
>It's very strange. So, does it mean the exception must be enabled if
>the throw_exception is used ?
Either enable exceptions or define BOOST_NO_EXCEPTIONS and provide a user
supplied throw_exception(). The user supplied throw_exception() presumably
terminates the program via std::abort() or similar function.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk