Re: Destructor not called with forward declaration instead of include

In article <fuuqcu$han$1@[EMAIL PROTECTED]
>, Seungbeom Kim
<musiphil@[EMAIL PROTECTED]
> wrote:

> > redesign the class hierarchy). Could the following be enough?
> > 
> >    virtual class Clazz; // I have a virtual destructor, promise!
> 
> I guess the compiler may need the complete class definition even
> just to invoke the virtual destructor; e.g. it has to know which
> entry in the vtable represents the destructor.
Probably true, the simplest is not to delete the incomplete class even
providing a holder

// NOT TESTED!!!!
class Holder
{
// everything provided private access.
// default cpy_ctor/assign probably ok...
// if not they are public access...

    class Incomplete;
    ~Holder();
    Holder(Incomplete *a):ptr(a){}
    Incomplete *ptr;
    friend class UsingClass;
};
or the like hides the dtor from anything but UsingClass as well as the
Incomplete type so  Holder can be copied. assigned and not deleted or
created outside of UsingClass.  So the problem disappears if the
implementation of UsingClass sees the complete implementation
of Incomplete and ~Holder() implementation....

-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]