This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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: Freeing xalloc'ed array

From: Paolo Carlini <pcarlini at suse dot de>
To: Paolo Carlini <pcarlini at suse dot de>
Cc: Akim Demaille <akim at epita dot fr>, libstdc++ at gcc dot gnu dot org
Date: Wed, 13 Oct 2004 15:04:28 +0200
Subject: Re: Freeing xalloc'ed array
References: <mv4mzyrqamw.fsf@nostromo.lrde.epita.fr> <416CF4BC.6030204@suse.de> <20041013114042.GA5591@compsoc.man.ac.uk> <mv4vfdeq0tv.fsf@nostromo.lrde.epita.fr> <416D224F.2070600@suse.de>

Paolo Carlini wrote:

"... The objects are /not/ destroyed during program execution."

... and Note 265 explains, rather convincigly, IMO:

   "Constructors and destructors for static objects can access these
   objects to read input from _stdin_ or write output to _stdout_
   or _stderr_."

Paolo.

References:
- Freeing xalloc'ed array
  - From: Akim Demaille
- Re: Freeing xalloc'ed array
  - From: Paolo Carlini
- Re: Freeing xalloc'ed array
  - From: Jonathan Wakely
- Re: Freeing xalloc'ed array
  - From: Akim Demaille
- Re: Freeing xalloc'ed array
  - From: Paolo Carlini

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