Is there any guarantee for the order in which C++ stack variables are destroyed

Question

Consider the following code:

{
  std::auto_ptr<Something> p1(pSomePointer);
  std::auto_ptr<Something> p2(pSomeOtherPointer);
  ...
}

Is there any guarantee that p2 destructor will be called before p1's when exiting the scope? Common sense says that the stack variables should be destroyed from top of the stack first but C++ compiler can reorder assignments.

Answer 1

Yes, they are destroyed in order opposite to the construction order - objects constructed last will be destroyed first. C++ guarantees this.