Warp wrote:
>   It would be difficult for the compiler to follow how the functions are
> being called (and, in fact, it's impossible for it to know if the pure
> virtual function actually gets called in the general case).

Especially if that function is already compiled and in a library 
somewhere. :-)

>   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.

You mean, undefined behavior as opposed to a core dump? ;-)

-- 
   Darren New / San Diego, CA, USA (PST)
     Remember the good old days, when we
     used to complain about cryptography
     being export-restricted?

Post a reply to this message