Difference between revisions of "Cpp Coding Standards/CLSINIT/NoVirt"
From Apache OpenOffice Wiki
B michaelsen (Talk | contribs) |
|||
| Line 3: | Line 3: | ||
When an object is still in construction or already partly destructed, virtual functions often do not point to the intended override, but to another implementation of that function, or even nowhere. Exact behaviour may be compiler dependent. | When an object is still in construction or already partly destructed, virtual functions often do not point to the intended override, but to another implementation of that function, or even nowhere. Exact behaviour may be compiler dependent. | ||
| + | [[Category:Coding Standards]] | ||
Latest revision as of 17:06, 14 December 2009
No Virtuals in Constructor or Destructor (NoVirt)
When an object is still in construction or already partly destructed, virtual functions often do not point to the intended override, but to another implementation of that function, or even nowhere. Exact behaviour may be compiler dependent.
