From: Enrico Weigelt <weigelt@metux.de>
To: gcc-help@gcc.gnu.org
Subject: Re: C++ and garbage collection
Date: Sat, 05 Feb 2011 14:37:00 -0000 [thread overview]
Message-ID: <20110205124139.GB29367@nibiru.local> (raw)
In-Reply-To: <AANLkTimjjJd52d6vy7H3+sv4h0Nj_Y-mPHTVnYBUc-b8@mail.gmail.com>
* Lawrence Crowl <crowl@google.com> wrote:
> If your problem is leaking memory, and you aren't playing games
> with your pointers, then you can just add in the Boehm collector,
> leaving the deletes in place. This approach will leave the program
> working pretty much as before, but with less memory.
>
> If your problem is using objects after you have freed them, then you
> have a much harder problem.
I simply want to get rid of the whole deallocation issue at all
(never having to care about this anymore, making the code smaller
and so easier to maintain).
> Many C++ programs do real work in the destructors (like closing
> files) and removing the delete operations would disable that code.
As said in my prev. mail: these are only few cases where this
matters (files on external storages which are mounted/unmounted
by the application) - these are only few, well known places,
which I easily could refactor.
> One viable approach is to modify the uses of pointers into shared_ptr
> (from TR1 or boost) and then add the Boehm collector. This process
> takes work, because changing all pointers won't work and changing
> none won't buy you anything.
Guess this would take a lot of work and add more dependencies
(than just the relatively small boehm-gc lib) ...
cu
--
----------------------------------------------------------------------
Enrico Weigelt, metux IT service -- http://www.metux.de/
phone: +49 36207 519931 email: weigelt@metux.de
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666
----------------------------------------------------------------------
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------
next prev parent reply other threads:[~2011-02-05 12:51 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 [this message]
2011-02-05 14:43 ` Jonathan Wakely
2011-02-05 14:56 ` Enrico Weigelt
2011-02-06 19:29 ` Florian Weimer
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=20110205124139.GB29367@nibiru.local \
--to=weigelt@metux.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).