
8 Jan
2005
8 Jan
'05
2:52 p.m.
John Maddock wrote:
Okay, so let's have BOOST_NO_RTTI defined when the compiler/environment does not support RTTI, and we can use it to turn off use of RTTI in some Boost components :)
But Peter is right, there are macros here... perhaps BOOST_NO_RTTI and BOOST_NO_DYNAMIC_RTTI, with the former implying the latter.
Sounds reasonable to me, but do we ever use RTTI in non-dynamic situations anyway?
I don't know, but Boost.Python could be set up to use a reduced set of capabilities when only "static" RTTI was available. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com