From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <alves.ped@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: enum pretty-printing support
Date: Wed, 11 Jan 2012 16:45:00 -0000 [thread overview]
Message-ID: <m3sjjm6vp2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F0C9EF1.7090602@gmail.com> (Pedro Alves's message of "Tue, 10 Jan 2012 20:26:25 +0000")
>>>>> "Pedro" == Pedro Alves <alves.ped@gmail.com> writes:
Pedro> Is the intention to have this printer do more than work
Pedro> with flag enums? Otherwise, I'd suggest naming it FlagEnumerationPrinter
Pedro> (or some such).
I made this change.
Thanks.
Tom
next prev parent reply other threads:[~2012-01-11 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 20:26 Tom Tromey
2012-01-10 20:28 ` Pedro Alves
2012-01-11 16:45 ` Tom Tromey [this message]
2012-01-10 21:19 ` Eli Zaretskii
2012-01-10 21:23 ` Jan Kratochvil
2012-01-10 22:00 ` Tom Tromey
2012-01-10 22:19 ` Tom Tromey
2012-01-10 23:52 ` Jan Kratochvil
2012-01-11 16:46 ` Tom Tromey
2012-01-11 21:03 ` Jan Kratochvil
2012-01-11 21:25 ` Tom Tromey
2012-01-16 18:44 ` Tom Tromey
2012-01-16 18:45 ` Eli Zaretskii
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=m3sjjm6vp2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=alves.ped@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).