From: Chris Moller <cmoller@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: pr9065 patch
Date: Wed, 10 Mar 2010 12:34:00 -0000 [thread overview]
Message-ID: <4B9791BB.7050804@redhat.com> (raw)
In-Reply-To: <83iq943jfr.fsf@gnu.org>
On 03/09/10 23:11, Eli Zaretskii wrote:
>> Date: Tue, 09 Mar 2010 15:38:30 -0500
>> From: Chris Moller<cmoller@redhat.com>
>>
>> This is the typeid thing.
>>
>> This patch implements typeid in gdb, letting users do things like
>>
>> p typeid(<expression>)
>> p typeid(<expression>).name()
>> p typeid(<expression>).__name
>> p typeid(<expression>).__is_pointer_()
>>
>> and the same thing for types (i.e., p typeid(<type>).name())
>>
>
> Thanks. I think this needs a suitable patch to the manual as well.
>
Okay, I'll add that for the final version. (There ar a couple of other
minor things I remembered after I sent the patch out yesterday, like
patching expprint.c to include the new opcode enums.)
next prev parent reply other threads:[~2010-03-10 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 20:38 Chris Moller
2010-03-10 4:11 ` Eli Zaretskii
2010-03-10 12:34 ` Chris Moller [this message]
2010-03-11 21:32 ` Tom Tromey
2010-03-12 14:22 ` Chris Moller
2010-03-22 12:19 ` pr9065 patch (the typeid thing) Chris Moller
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=4B9791BB.7050804@redhat.com \
--to=cmoller@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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