class A
{
  std::string a;
  std::auto_ptr<int> b;
public:
  A()
  : a("")
  , b(new int)  
  {
    throw std::exception();
    // будут вызваны деструкторы для a и для b
  }

  ~A()
  {
    // деструктор никогда не будет вызыван, поскольку конструктор никогда не завершит работу
  }
};

int main()
{
  try 
  {
    std::string bb;
    A a;
  }
  catch(std::exception&)
  {
    // будет вызыван деструктор для bb
  }
}

A>class A
A>{
A>  std::string a;
A>  std::auto_ptr<int> b;
A>public:
A>  A()
A>  : a("")
A>  , b(new int)  
A>  {
A>    throw std::exception();
A>    // будут вызваны деструкторы для a и для b
A>  }

A>  ~A()
A>  {
A>    // деструктор никогда не будет вызыван, поскольку конструктор никогда не завершит работу
A>  }
A>};

A>int main()
A>{
A>  try 
A>  {
A>    std::string bb;
A>    A a;
A>  }
A>  catch(std::exception&)
A>  {
A>    // будет вызыван деструктор для bb
A>  }
A>}

A>

class A
{
  std::string a;
  std::auto_ptr<int> b;
public:
  A()
  : a("")
  , b(new int)  
  {
    throw std::exception();
    // будут вызваны деструкторы для a и для b
  }

  ~A()
  {
    // деструктор никогда не будет вызыван, поскольку конструктор никогда не завершит работу
  }
};

int main()
{
  A * a;
  try 
  {
    std::string bb;
    a = new A;
  }
  catch(std::exception&)
  {
    // будет вызыван деструктор для bb
    //нужен ли здесь delete a; ?
  }
}

КР>Тебя перестанут мучить твои сомнения

int foo(std::auto_ptr<C>, std::auto_ptr<C>);
int main()
{
  foo(std::auto_ptr<C>(new C()), std::auto_ptr<C>(new C()));
}

Beginning in Visual C++ .NET 2002, the CRT's new function (in libc.lib, libcd.lib, libcmt.lib, libcmtd.lib, msvcrt.lib, and msvcrtd.lib) will continue to return NULL if memory allocation fails. However, the new function in the Standard C++ Library (in libcp.lib, libcpd.lib, libcpmt.lib, libcpmtd.lib, msvcprt.lib, and msvcprtd.lib) will support the behavior specified in the C++ standard, which is to throw a std::bad_alloc exception if the memory allocation fails.

Normally, if you #include one of the C++ standard headers, like <new>, you'll get a /defaultlib directive in your object that will reference the appropriate C++ Standard Library according to the CRT model you used (the /M* compiler options). Generally, that will cause the linker to use the throwing operator new from the C++ Standard Library instead of the nonthrowing one from the main CRT, because the order of defaultlib directives will cause libcp.lib to be searched before libc.lib (under /ML).

An object that is partially constructed or partially destroyed will have destructors executed for all of its fully constructed subobjects, that is, for subobjects for which the constructor has completed execution and the destructor has not yet begun execution. Should a constructor for an element of an automatic array throw an exception, only the constructed elements of that array will be destroyed. If the object or array was allocated in a new-expression, the matching deallocation function (3.7.3.2, 5.3.4, 12.5), if any, is called to free the storage occupied by the object.

//skipped