🚀 go-pugleaf

The draft WP says that [section class.cdtor:3]

  When  a  virtual function is called directly or indirectly from a con-
  structor (including from its ctor-initializer) or from  a  destructor,
  and the object to which the call applies is the object under construc-
  tion or destruction, the function called is the  one  defined  in  the
  constructor  or destructor's own class or in one of its bases, but not
  a function overriding it in a class derived from  the  constructor  or
  destructor's  class, or overriding it in one of the other base classes
  of the complete object (_intro.object_).

Why allow this, rather than refusing calls to virtual functions at
all? It would be nice to say that `if I override this function, then
the old version will _never_ be called on objects of this type'.

--
-Geoff Keating (keagchon@mehta.anu.edu.au)

---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]