
20 Aug
2008
20 Aug
'08
4:03 p.m.
Quoting Robert Ramey <ramey@rrsd.com>:
It looks like for some compilers, the preprocessor macros alter the behavior to disabled - even though those compilers actually can throw exceptions so the new behavior is even more complex and arbitrary than I thought.
Are you sure? To make sure we are on the same page, I am looking at: http://svn.boost.org/trac/boost/browser/branches/release/boost/throw_excepti... An exception is not thrown if and only if BOOST_NO_EXCEPTIONS is defined. This has always been the case. It sounds like you are interpreting "BOOST_EXCEPTION_DISABLE defined" to mean "exception not thrown" but that's not the case. It merely disables the new functionality the Boost.Exception library.