From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [5/10] RFC: implement "typeid"
Date: Wed, 06 Mar 2013 21:38:00 -0000 [thread overview]
Message-ID: <83fw081a6d.fsf@gnu.org> (raw)
In-Reply-To: <87lia0jk24.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Date: Wed, 06 Mar 2013 14:27:15 -0700
>
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -36,6 +36,8 @@ Lynx 178 PowerPC powerpc-*-lynx*178
>
> * 'info proc' now works on some core files.
>
> +* GDB now implements the the C++ 'typeid' operator.
> +
> * Python scripting
>
OK for this part. Thanks.
prev parent reply other threads:[~2013-03-06 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 21:27 Tom Tromey
2013-03-06 21:38 ` Eli Zaretskii [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=83fw081a6d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@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