Excaption in Derived Constructors?

I have a question regarding exceptions in contructors.

Picture that I have the following class:

Code:

class BaseObject
{
public:
  BaseObject();
  virtual ~BaseObject();
};

Now I have a simple derived class as follows:

Code:

class DerivedObject : public BaseObject
{
  DerivedObject();
  virtual ~DerivedObject();
};

What happens if an exception is thrown within the constructor of the DerivedObject, like so:

Code:

DerivedObject::DerivedObject()
  : BaseObject()
{
  // Contructor - do something
  try
  {
    ...
    ...
  
    // EXCEPTION THROWN HERE
    ...
  }
  catch(...)
  {
    // Free newly created heap objects
  }
}

I am familiar with catching exceptions within constructors to prevent memory loss. However, in this specific case, will the destructor of the BaseObject be called automatically after the exception is thrown?

My guess is that it won't, but I'm not sure. Should I ensure that I free any memory held by BaseObject in the catch block of DerivedObject constructor?

Edit : Oops there was an exception in the title of this thread.

The base object will have its constructor called and will be totally constructed before the derived constructor is called. As the base object is contructed, it's destructor is called if you catch the exception outside of the class...so yes, base will be freed...

Unfortunately, a destuctor will only be called on a fully constructed object, so you may find your problems will be with derived if you have allocated resources in the construtor before throwing the exception (assuming you cant rescue the situation by catching the exception in the constructor and allowing the constructor to return)...

Scott Meyers, discusses this situation in More Effective C++ along with numerous workarounds and tips to avoid leaks from throwing exceptions in constructors.......

Thanks Fordy. So if I have the following code:

Code:

DerivedObject* dobj = new DerivedObject();

and an exception is thrown in the DerivedObject constructor*, but after the BaseObject constructor has been completed (as above), then the BaseObject destructor will be called. Is this correct?

*And the DerivedObject constructor re-throws the exception in the catch block, after it is cleared up any memory allocated.

Do you follow that?

Read this........ then buy all of herb sutters books.

Thanks to you both. I also tested it with some dummy code.

Originally posted by Davros

I am familiar with catching exceptions within constructors to prevent memory loss. However, in this specific case, will the destructor of the BaseObject be called automatically after the exception is thrown?

Are you rethrowing the exception in the catch(...) handler?
If not, then the constructor will return successfully and the object will be constructed.

Yes, but forgot to include it in my previous code samples.

Thanks for the thought.