From: Roland McGrath <roland@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: feature idea: type nicknames
Date: Fri, 03 Jul 2009 19:38:00 -0000 [thread overview]
Message-ID: <20090703193755.9F86446126@magilla.sf.frob.com> (raw)
In-Reply-To: Tom Tromey's message of Friday, 3 July 2009 10:34:32 -0600 <m3prchybc7.fsf@fleche.redhat.com>
> We looked into this particular sub-problem a little. Our idea was
> that it would be nice if "ptype x" showed exactly what the user wrote
> in the declaration of "x".
Yes, that's the ideal default. The "shortest way to say it" heuristic is a
"better than nothing" idea for the default given limitations on what gdb
can/does figure out from the DWARF. (I think the manually user-added
nicknames would be nice too. Sometimes what I wrote in the source is a bit
long to use a hundred times in a long debugging session.)
> In the end it seems that GCC usually emits the verbose forms. I filed
> a gcc bug report about this; but it isn't completely clear that this
> is what we actually want (see last comment):
I don't really follow what that comment says, but I concur that this
qualifies as "isn't completely clear". :-)
> Another idea would be to suppress printing of defaulted template
> parameters by default. I don't think we've researched that yet.
Yes, I think that is obviously desireable.
> (I assume we'll get into the usual problems: DWARF still can't represent
> everything, and anyway even if it could, GCC doesn't emit it :-)
Got to push on the stack from one end or the other to make it move.
Thanks,
Roland
prev parent reply other threads:[~2009-07-03 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 0:21 Roland McGrath
2009-07-03 16:34 ` Tom Tromey
2009-07-03 19:38 ` Roland McGrath [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=20090703193755.9F86446126@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).