From: Doug Evans <dje@sebabeach.org>
To: gdb-patches@sourceware.org
Subject: Re: [patch] Create cleanups.[ch]
Date: Mon, 16 Apr 2012 02:07:00 -0000 [thread overview]
Message-ID: <m3fwc4hhbr.fsf@annie.sebabeach.org> (raw)
I wrote:
> Since cleanups are a big enough source of issues, I want to separate them out.
> This patch moves the core cleanup API into its own file.
> It makes no other changes.
> I have at least one more patch to go, but I want to get this done first.
> [...]
> +/* WARNING: The result of the "make cleanup" routines is not the intuitive
> + choice of being a handle on the just-created cleanup. Instead it is an
> + opaque handle of the cleanup mechanism and represents all cleanups created
> + from that point onwards.
> + The result is guaranteed to be non-NULL though. */
Heh, I'm getting ahead of myself. :-)
Ignore the last sentence there.
The wording of the previous sentence is fine with me, but one may
prefer it to say something along the lines of being the handle of
the previous cleanup ("old_chain") or something like that, or say
nothing at all other than being an opaque handle.
next reply other threads:[~2012-04-15 20:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 2:07 Doug Evans [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-15 20:27 Doug Evans
2012-04-16 7:27 ` Sergio Durigan Junior
2012-04-16 10:52 ` Pedro Alves
2012-04-16 19:11 ` Sergio Durigan Junior
2012-04-18 9:43 ` Pedro Alves
2012-04-19 17:37 ` Sergio Durigan Junior
2012-04-20 15:09 ` Pedro Alves
2012-04-16 20:06 ` Tom Tromey
2012-04-16 20:42 ` Pedro Alves
2012-04-16 20:59 ` Tom Tromey
2012-04-17 22:41 ` Doug Evans
2012-04-16 20:10 ` Tom Tromey
2012-04-17 22:54 ` Doug Evans
2012-04-17 22:59 ` Joel Brobecker
2012-04-18 4:26 ` Sergio Durigan Junior
2012-04-18 6:22 ` Joel Brobecker
2012-04-16 10:40 ` Pedro Alves
2012-04-18 14:02 ` Yao Qi
2012-04-18 14:32 ` Tom Tromey
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=m3fwc4hhbr.fsf@annie.sebabeach.org \
--to=dje@sebabeach.org \
--cc=gdb-patches@sourceware.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