Well, that was why I had my suggested sample pseudocode restore the previous vtable pointer before calling down to the next function (and put itself back when that's done).
That has reentrancy issues, unfortunately. Potentially threading and DOD issues as well. Keeping the vtable reasonably immutable's in our best interests.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
