On Sun, Jun 20, 2010 at 11:20 PM, Joel Falcou
Emil Dotchevski wrote:
Boost Exception does support the error info functionality even in BOOST_NO_EXCEPTIONS builds. For example, the user-defined boost::throw_exception function can use boost::diagnostic_information.
so I can grab the textual contents of diagnostic_info and do w/e with it.
Yes.
So I don't think it'd be easy at all to de-STL the Boost Exception library. Also note that BOOST_NO_EXCEPTIONS builds still require the exception types to derive from std::exception.
I kinda feared that. Guess I'll for no-exceptions on machine where std is a no-go and remove the intermediate level.
You can define BOOST_EXCEPTION_DISABLE, which disables the Boost Exception library itself, leaving the legacy boost::throw_exception behavior (which still has two flavors, depending on BOOST_NO_EXCEPTIONS). In this configuration no STL components are used except for std::exception. You can then #ifdef your code that uses the Boost Exception library with BOOST_EXCEPTION_DISABLE. HTH, Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode