public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: feature idea: type nicknames
Date: Fri, 03 Jul 2009 16:34:00 -0000	[thread overview]
Message-ID: <m3prchybc7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090703002049.C49F1404FD@magilla.sf.frob.com> (Roland McGrath's message of "Thu\,  2 Jul 2009 17\:20\:49 -0700 \(PDT\)")

>>>>> "Roland" == Roland McGrath <roland@redhat.com> writes:

[...]
Roland> appears in *my* code nowhere in a form longer than:

Roland> std::map<int, elfutils::dwarf_data::attr_value<elfutils::dwarf_edit, elfutils::dwarf_data::value<elfutils::dwarf_edit> > >::const_iterator

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".

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):

    http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37590

Another idea would be to suppress printing of defaulted template
parameters by default.  I don't think we've researched that yet.  (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 :-)

Roland> What makes sense to me is that the STL pretty printer module can also
Roland> have "type name pretty-printers".

Interesting idea.  Maybe it is time to resurrect the currently-defunct
type-printing task.

Tom

  reply	other threads:[~2009-07-03 16:34 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 [this message]
2009-07-03 19:38   ` Roland McGrath

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=m3prchybc7.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=roland@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).