Emil Dotchevski wrote:
I don't need to search, I remember very well. :)
In its initial release (1.36), Boost Exception did not support BOOST_NO_RTTI configurations, which seemed reasonable because most compilers require RTTI for exception handling.
wow- that's something I never knew
The workaround was to #define BOOST_EXCEPTION_DISABLE under BOOST_NO_RTTI. A permanent fix was committed to trunk two weeks later, and released with 1.37.
Faced with the initial problem, Robert's knee-jerk reaction was to not call boost::throw_exception at all. He changed Boost Serialization, making it incompatible with all previous releases under BOOST_NO_EXCEPTIONS.
Someone pointed out Robert's mistake, which he corrected, but not before it got out with the following Boost release (1.37), in which Boost Serialization had his flawed (and unnecessary) workaround, requiring BOOST_NO_EXCEPTIONS users of Boost Serialization to make changes in their code. They had to revert those changes for 1.38.
Well, I remember it all very differently. Not that it matters. Robert Ramey
That was the end of it (or so I thought.)
Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost