From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Fission patch 1/2
Date: Fri, 13 Apr 2012 19:46:00 -0000 [thread overview]
Message-ID: <CADPb22R0WhdVb+ArY_bhtQC8bxFSxUmqybTRxAFCz7xDXLmOeA@mail.gmail.com> (raw)
In-Reply-To: <87obqvwmay.fsf@fleche.redhat.com>
On Fri, Apr 13, 2012 at 10:53 AM, Tom Tromey <tromey@redhat.com> wrote:
> Though I'd still prefer that most
> code not play games with cleanups at all and just treat them as
> block-scoped as much as possible.
cleanups are chained, and one has to always be cognizant of the chain
(in a not-entirely intuitive fashion IMO, though I understand the
implementation reasons for it).
I think there's value in a cleanup mechanism where one didn't have to
be cognizant of the chain, or at least be less cognizant (whether
that's completely possible, I don't know).
[btw, I don't know if I'd color it as "playing games" ...]
prev parent reply other threads:[~2012-04-13 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 7:44 Doug Evans
2012-04-13 17:12 ` Tom Tromey
2012-04-13 17:30 ` Doug Evans
2012-04-13 18:11 ` Tom Tromey
2012-04-13 19:46 ` Doug Evans [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=CADPb22R0WhdVb+ArY_bhtQC8bxFSxUmqybTRxAFCz7xDXLmOeA@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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