From: Tom Tromey <tromey@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Project Archer <archer@sourceware.org>
Subject: Re: $n for pretty-printed elements?
Date: Fri, 17 Jul 2009 22:05:00 -0000 [thread overview]
Message-ID: <m3ljmn3r01.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090629000709.45C9C420F6@magilla.sf.frob.com> (Roland McGrath's message of "Sun\, 28 Jun 2009 17\:07\:09 -0700 \(PDT\)")
Sorry for the delay in replying to this.
I'm very behind :(
Roland> Consider:
Roland> (gdb) p _m_path
Roland> $161 = std::list = {
Roland> [0] = {
[...]
Roland> (gdb) p _m_path
Roland> $161 = std::list = {
Roland> [0] = $162 = {
This seems like a good idea to me.
There are some subtleties. We may be seeing the result of several
printers there. E.g., consider a std::list<std::string>. I think for
that we'd see:
$61 = std::list = {
[0] = $162 = "hi bob";
};
... where I suppose $162 would refer to the char* underneath it all.
I suppose my point is that there are some operations, like assignments,
which wouldn't always make sense.
I'll put this on my list.
Tom
next prev parent reply other threads:[~2009-07-17 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 0:07 Roland McGrath
2009-06-29 3:46 ` Paul Pluzhnikov
2009-07-17 22:05 ` Tom Tromey [this message]
2009-07-20 6:22 ` 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=m3ljmn3r01.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).