From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: RFC: introduce scoped cleanups
Date: Tue, 16 Jul 2013 20:33:00 -0000 [thread overview]
Message-ID: <874nbujlcq.fsf@fleche.redhat.com> (raw)
In-Reply-To: <87wqq8ih9u.fsf@fleche.redhat.com> (Tom Tromey's message of "Wed, 05 Jun 2013 11:44:45 -0600")
Joel> Regardless of the above, I like the idea of performing the cleanups
Joel> on an obstack; fast and yet a little more resilient to programming
Joel> errors. Not sure if that would be something easy to implement or not,
Joel> though.
Tom> It ought to be easy. I will look into it.
I think it is easy to implement. And, I think I've convinced myself
that it is safe. But it seems to me that we could keep a freelist
instead -- this is much more obviously safe, and also, I think,
reasonably fast in most cases. So I think I'm more inclined to take
this approach instead.
Tom
prev parent reply other threads:[~2013-07-16 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 18:56 Tom Tromey
2013-05-30 20:09 ` Tom Tromey
2013-05-31 6:11 ` Joel Brobecker
2013-05-31 15:56 ` Tom Tromey
2013-05-31 16:15 ` Pedro Alves
2013-05-31 20:24 ` Tom Tromey
2013-06-03 6:07 ` Joel Brobecker
2013-06-05 17:44 ` Tom Tromey
2013-07-16 20:33 ` Tom Tromey [this message]
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=874nbujlcq.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/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