Warp wrote:

>   The problem with calling a pure virtual function in the base class
> constructor is that the derived class has yet not been initialized and
> thus calling a derived class function implementation could cause undefined
> behavior because it's not constructed.

Um... probably. You know way more about C++ than I ever will.

Either way, it's definitely a program bug, and it's definitely 
completely unrelated to virtual memory. ;-)

Post a reply to this message