🚀 go-pugleaf

Why is the destructor only called for fully contructed objects?
To my oppinion this results in code duplication in the contructor and destructor

For example:


class a
{
public:
   char* mBuffer1;
   char* mBuffer2;
   a();
   ~a();
};

a::a()
{
   mBuffer1 = NULL;
   mBuffer2 = NULL;

   try
   {
      mBuffer1 = new char[1000];
      if(mBuffer1 == NULL)
         throw MemError;

      mBuffer2 = new char[1000];
      if(mBuffer1 == NULL)
         throw MemError;
   }
   catch(...)  // allocation failed
   {
      delete mBuffer1;  
      delete mBuffer2;

      throw;
   }

}

a::~a()
{
   delete mBuffer1;
   delete mBuffer2;
}

If the destructor would be called in case of incomplete contruction, the
code would be much simpler, even in this small example.

a::a()
{
   // initialize for save destruction
   mBuffer1 = NULL;
   mBuffer2 = NULL;

   mBuffer1 = new char[1000];
   if(mBuffer1 == NULL)
      throw MemError;

   mBuffer2 = new char[1000];
   if(mBuffer1 == NULL)
      throw MemError;
 }

// this would be called in case of an exception
// if for example the mBuffer2 allocation failed
a::~a()
{
   delete mBuffer1;
   delete mBuffer2;
}

So, why not call a destructor if an object is partially contructed?

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