This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Order of Object destruction

From: Eljay Love-Jensen <eljay at adobe dot com>
To: Neophytos Michael <nmichael at cs dot princeton dot edu>
Cc: gcc-help at gcc dot gnu dot org
Date: Fri, 23 May 2003 08:56:41 -0500
Subject: Re: Order of Object destruction
References: <4.3.2.7.2.20030523070720.00b3fa40@iplan-mn.corp.adobe.com><4.3.2.7.2.20030523070720.00b3fa40@iplan-mn.corp.adobe.com>

Hi Neophytos,

>When the call foo(a) is made the copy constructor is called and makes a new object "z". This object "z" is supposed to be desposed off when it goes out of scope.

Correct. And it does. Temporary object "z" goes out of scope at the caller's semi-colon.

Returned object "b" also goes out of scope at the caller's semi-colon.

>I was asking which was supposed to be desposed of first "z" or "b"?

I think it is up to the discretion of the compiler's vendor whether it's a LIFO object destruction at the semi-colon, or FIFO object destruction.

Sincerely,
--Eljay

Follow-Ups:
- Re: Order of Object destruction
  - From: LLeweLLyn Reese

References:
- Re: Order of Object destruction
  - From: Eljay Love-Jensen
- Re: Order of Object destruction
  - From: Neophytos Michael

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]