This is the mail archive of the gcc@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: adding destroyable objects into Ggc

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: Basile Starynkevitch <basile at starynkevitch dot net>
Cc: Ian Lance Taylor <iant at google dot com>, gcc at gcc dot gnu dot org
Date: Tue, 18 Oct 2011 18:46:14 +0100
Subject: Re: adding destroyable objects into Ggc
References: <20111018171201.361304028ab94f102f827bd2@starynkevitch.net> <mcr62jm5kcb.fsf@coign.corp.google.com> <20111018191350.470cd6b1cd291373d5ff3f2c@starynkevitch.net> <CAKOQZ8wG63auJXYnVbRrOUAcyOtj5vLQ0KgBg8whZ6tWi7Kb1w@mail.gmail.com> <20111018194123.1d5103e320cbed0a35363349@starynkevitch.net>

On 18 October 2011 18:41, Basile Starynkevitch wrote:
>
> However, I don't know very well auto_ptr. ?Could you explain to use how do they deal with
> *circular* memory references.... (perhaps by taking as examples code inside GCC).
> My feeling is that auto_ptr is not able to deal with them, but I'll be delighted to be
> proven wrong.

Noone except you mentioned auto_ptr.

Something like shared_ptr is a better choice in some cases, and its
companion weak_ptr can be used to break cycles.

References:
- adding destroyable objects into Ggc
  - From: Basile Starynkevitch
- Re: adding destroyable objects into Ggc
  - From: Ian Lance Taylor
- Re: adding destroyable objects into Ggc
  - From: Basile Starynkevitch
- Re: adding destroyable objects into Ggc
  - From: Ian Lance Taylor
- Re: adding destroyable objects into Ggc
  - From: Basile Starynkevitch

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