virtual functions and dynamic binding

[mescaline]

If a function is declared a virtual function, in what cases will
(some) compilers still do static binding?

thanks

[Victor Bazarov]

"mescaline" <ap*****@columb ia.edu> wrote...

If a function is declared a virtual function, in what cases will
(some) compilers still do static binding?

All compilers bind statically if a virtual function is called
from a constructor or a destructor, or if it's called using
fully qualified name (IIRC).

Victor

[Ron Natalie]

"Victor Bazarov" <v.********@com Acast.net> wrote in message news:fLKHb.108$ xX.800@attbi_s0 2...
\

All compilers bind statically if a virtual function is called
from a constructor or a destructor,

Only if called directly from the constructor or destructor. However,
virtual functions are not disabled during construction, the only thing that
changes is that the effective type of the object is the class that the constructor
/destructor is being executed for.

struct B {
virtual void v();
void nv() { v(); }
};

struct D : B {
void v();
D() { nv(); } // results in D::v() getting called.

[Nick Hounsome]

"mescaline" <ap*****@columb ia.edu> wrote in message
news:e5******** *************** ***@posting.goo gle.com...

If a function is declared a virtual function, in what cases will
(some) compilers still do static binding?

When they know what the actual function must be - e.g ctor,dtor or just

X x;
x.aVirtualFunct ion();
thanks