The exception library uses std::type_info objects as keys for accessing the values transported by boost::exception objects, and that's where typeid is needed. It is possible to disable the data-transporting functionality only, leaving the exception_ptr functionality available even with BOOST_NO_TYPEID, but compilers need some RTTI functionality to implement exception handling so I am not sure if an exception handling library makes sense at all when RTTI is disabled. I think the best option is to #define BOOST_EXCEPTION_DISABLE if BOOST_NO_TYPEID is defined. What is the correct way to do this, or should I directly #ifdef based on either BOOST_EXCEPTION_DISABLE / BOOST_NO_TYPEID? Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode On Tue, Jul 1, 2008 at 7:46 AM, Daniel James <daniel_james@fmail.co.uk> wrote:
Using boost with RTTI disabled was recently discussed on the user list, and I had a quick look into it. It seems that shared_ptr added support for the BOOST_NO_TYPEID macro in 1.35:
http://svn.boost.org/trac/boost/ticket/1108
But because it now depends on the new exception library, which requires RTTI, it no longer works. Would it be possible to support the macro in Boost.Exception?
Daniel _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost