
On 12/14/16 6:06 PM, Nat Goodspeed wrote:
On Wed, Dec 14, 2016 at 7:53 PM, Robert Ramey
wrote: I think that there has been a lot of confusion about what BOOST_THROW_EXCEPTION is suppose to do.
My understanding was that it was a macro intended to support the writing of portable code that could run on platforms which didn't support exceptions or where the user / author didn't want to use the exception mechanism so he could redefine the macro. Lot's of libraries used this idiom to decouple their libraries from the the selection of exception mechanism.
I admit that my usage of BOOST_THROW_EXCEPTION is fairly recent, but that use case is not even mentioned: http://www.boost.org/doc/libs/1_62_0/libs/exception/doc/BOOST_THROW_EXCEPTIO...
Right. Because the semantics of BOOST_THROW_EXCEPTION were changed and the documentation updated to the new semantics. The history of the current version only goes back to 2009 so it's not visible now. Robert Ramey