On Mon, 2008-01-07 at 09:19 +0100, Stephan Bergmann wrote: > 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?
Ah, good point. So, I'll need to go up in the whole class inheritance tree then. Now, that's when it gets nasty; if the inheritance tree involves more than one module, that may cause a cascade of necessary code re-writes across many modules... Yikes. :-( The following macros appear to be the major consumers of TYPEINFO: TYPE ISA PTR_CAST So, we'd probably watch out for their usage when removing TYPEINFO altogether. Kohei -- Kohei Yoshida - OpenOffice.org Engineer - Novell, Inc. <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
