From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, tromey@redhat.com
Cc: Chris Moller <cmoller@redhat.com>
Subject: Re: PR11067 patch
Date: Mon, 08 Feb 2010 22:32:00 -0000 [thread overview]
Message-ID: <201002082232.39279.pedro@codesourcery.com> (raw)
In-Reply-To: <m3aavj4cmp.fsf@fleche.redhat.com>
On Monday 08 February 2010 21:54:22, Tom Tromey wrote:
> >>>>> "Chris" == Chris Moller <cmoller@redhat.com> writes:
>
> Chris> The attached patch fixes bug 11067 "p <enum constant> should print the
> Chris> constant's value" by providing a means of setting a format string to
> Chris> be used in printing enums. The string is set with
>
> Chris> set enum-fmt <string>
>
> I would rather not introduce a new option for this, particularly a
> formatting option. We don't have this sort of thing elsewhere in gdb --
> we just pick a printing format or two.
Ditto.
> I re-read the thread on the archer list. I propose having it print
> like:
>
> $2 = ENUMERATOR = (enum tag) 23
>
> However, i would suppress the extra stuff in structs and when printing
> in summary mode.
I seriously don't want to start a bikeshed, but,
IMO, I don't think it's a good idea to to invent new
output syntax for this. There's no need to print the type of
the enum, that's what ptype is for. And we don't do it for any
other type.
We can look at enum's as having both a numeric facet, and
a symbolic facet, just like "char"s, and those we print as
(gdb) p 'a'
$1 = 97 'a'
If I had a choice, I would make printing enums exactly like:
$2 = 23 'ENUMERATOR'
This is short, concise, and models existing output. It
should look obvious what that output means.
And then users don't have to learn to recognize/identify
different outputs depending on where the type is
embedded or printed. That sounds important usability
wise to me.
Has this option seriously been discarded?
--
Pedro Alves
next prev parent reply other threads:[~2010-02-08 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 13:37 Chris Moller
2010-02-06 19:40 ` Eli Zaretskii
2010-02-08 21:54 ` Tom Tromey
2010-02-08 22:08 ` Chris Moller
2010-02-08 22:32 ` Pedro Alves [this message]
2010-02-08 22:47 ` Chris Moller
2010-02-08 23:25 ` Pedro Alves
2010-02-09 4:13 ` Eli Zaretskii
2010-02-09 4:13 ` Joel Brobecker
2010-02-09 17:31 ` Chris Moller
2010-02-09 23:48 ` Tom Tromey
2010-02-10 3:03 ` Chris Moller
2010-02-10 8:19 ` Joel Brobecker
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=201002082232.39279.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=cmoller@redhat.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