The BeOS userland api had base classes with reserved functions that were there solely to reserve space in the objects vtable becase of the fragile base class pr

The BeOS userland api had base classes with reserved functions that were there solely to reserve space in the objects vtable becase of the fragile base class problem: http://en.wikipedia.org/wiki/Fragile_binary_interface_problem http://en.wikipedia.org/wiki/Fragile_binary_interface_proble... I wonder how modern C++ frameworks are handling this?