From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [doc patch] whatis vs. ptype - the difference
Date: Tue, 19 Jul 2011 13:52:00 -0000 [thread overview]
Message-ID: <201107191427.59516.pedro@codesourcery.com> (raw)
In-Reply-To: <20110715153335.GA25834@host1.jankratochvil.net>
On Friday 15 July 2011 16:33:35, Jan Kratochvil wrote:
> (*) That is a class typedef, not a subject of ptype unrolling. class typedef
> is IMO an uncommon construct:
> class C { typedef int t; t i; } c;
It is very common with templates, things like:
template<class T> struct Foo {
typedef std::map<std::string, T> MapType;
...
};
--
Pedro Alves
next prev parent reply other threads:[~2011-07-19 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 19:20 Jan Kratochvil
2011-07-12 20:28 ` Eli Zaretskii
2011-07-12 20:38 ` Jan Kratochvil
2011-07-12 20:43 ` Eli Zaretskii
2011-07-12 20:30 ` Tom Tromey
2011-07-15 14:17 ` Eli Zaretskii
2011-07-15 18:07 ` Jan Kratochvil
2011-07-19 13:52 ` Pedro Alves [this message]
2011-07-26 2:58 ` ping: " Jan Kratochvil
2011-07-26 8:36 ` Eli Zaretskii
2011-07-26 18:11 ` Jan Kratochvil
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=201107191427.59516.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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