Why do un-named C++ objects destruct before the scope block ends?

Question

The following code prints one,two,three. Is that desired and true for all C++ compilers?

class Foo
{
      const char* m_name;
public:
      Foo(const char         


        

Answer 1

The scope of a temporary object like that is just one line. Think about it, you can no longer reference it after the line ends, so why would the object remain around?

If this weren't the case, compilers wouldn't be able to optimize out temporary objects in function calls.