Kohei Yoshida wrote:
On Fri, 2008-01-04 at 20:03 +0100, Oliver Specht wrote:
I wouldn't do this before all uses of IS_TYPE, TYPEID, PTR_CAST etc. are
removed. If you just remove the TYPEINFO and TYPEINITn macros a lot of
code will break.
I'm not sure if I agree. Since they are macros & get expanded before
the code gets compiled, the compiler should give us an error and the
build should fail if there is any breakage (such as PTR_CAST being used
when no TYPEINFO is given etc).
Without looking at the actual macros: Would that strategy really work
if you keep the macros in a base class definition and remove them from a
derived class definition?
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]