public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: gcc-help@gcc.gnu.org
Subject: Re: C++ and garbage collection
Date: Sun, 06 Feb 2011 19:29:00 -0000	[thread overview]
Message-ID: <87d3n5e1tg.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20110205144610.GA14734@nibiru.local> (Enrico Weigelt's message	of "Sat, 5 Feb 2011 15:46:10 +0100")

* Enrico Weigelt:

>> GCC includes a tr1::shared_ptr so there's no extra dependency if you
>> are only planning to use g++, and std::shared_ptr is part of C++0x.
>
> How does that one actually work and what do I have to do to use it ?

What's the oldest GCC version you're targeting?

Modern GCC has std::unique_ptr (zero-overhead pointer wrapper with
RAII semantics), std::shared_ptr and std::make_shared (avoiding a
separate allocation using operator new).  This should work after some
adjustments, as long as your data structures are acyclic.  You just
have to avoid taking short-cuts to optimize things, using references
and plain pointers instead of the std:: wrappers.  In this regard,
Boehm GC is hard to beat.

  reply	other threads:[~2011-02-06 13:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 20:25 Enrico Weigelt
2011-02-04 22:13 ` Florian Weimer
2011-02-05 12:51   ` Enrico Weigelt
2011-02-05  0:03 ` Jonathan Wakely
2011-02-05  4:25 ` Lawrence Crowl
2011-02-05 14:37   ` Enrico Weigelt
2011-02-05 14:43     ` Jonathan Wakely
2011-02-05 14:56       ` Enrico Weigelt
2011-02-06 19:29         ` Florian Weimer [this message]
2011-02-07  6:41           ` Enrico Weigelt
2011-02-07 18:50             ` Florian Weimer
2011-02-12 20:55               ` Enrico Weigelt
2011-02-06 23:01         ` Jonathan Wakely

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d3n5e1tg.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=gcc-help@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).