IanB
28th October 2005, 03:52
Dear all,
Just stumbled over a serious annoyance in the way MS VC++ builds it's vtables.
Normally vtables are built in the order of first declaration, so adding new pure virtual method to the end of the class declaration allows easy extension and backwards binary compatibility. However when overloading method calls the compiler groups all the vtable entries for that method name together, positioned at the first declaration, sorted by argument signature string. :angry:
The recent addition of the planar arguments overload of IscriptEnvironment::SubFrame() has sadly bitten us very severly.
Live and learn :o
IanB
Just stumbled over a serious annoyance in the way MS VC++ builds it's vtables.
Normally vtables are built in the order of first declaration, so adding new pure virtual method to the end of the class declaration allows easy extension and backwards binary compatibility. However when overloading method calls the compiler groups all the vtable entries for that method name together, positioned at the first declaration, sorted by argument signature string. :angry:
The recent addition of the planar arguments overload of IscriptEnvironment::SubFrame() has sadly bitten us very severly.
Live and learn :o
IanB