Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Elmenthaler\, Jens" <jens.elmenthaler@verigy.com>
Cc: <gdb@sourceware.org>
Subject: Re: Python pretty printers and dynamic cast
Date: Tue, 05 Jan 2010 15:34:00 -0000	[thread overview]
Message-ID: <m3hbr0bm6k.fsf@fleche.redhat.com> (raw)
In-Reply-To: <58596C4646708B4BB990C44839973330017EFAE8@usplmvpbe001.ent.rt.verigy.net> 	(Jens Elmenthaler's message of "Tue, 22 Dec 2009 02:14:26 -0600")

>>>>> "Jens" == Elmenthaler, Jens <jens.elmenthaler@verigy.com> writes:

Tom> There is nothing built-in yet.  We've had a few requests for this,
Tom> though, and there was a patch posted to the archer list.  If you give it
Tom> a try, let us know how it turns out.

[...]
Jens> So, my vote as a user looks something like this:
Jens> Prio 1: commit this patch for the rtti_type method (I applied it
Jens> to the current gdb 7.0 sources and was happy with it). ]

I'm hoping we'll merge a bunch of python stuff "soon".
I'll make sure this is on our list.

Jens> Prio 2: also add the C++ style casts to improve gdb command line
Jens> experience for C++.

FWIW we have a patch to add these casts on the expr-cumulative branch.
I will look into merging that.

Jens> Prio 3: provide the C++ style casts in the Python API to make
Jens> pretty printers like the one described above clean.

Could you file a feature request for this in bugzilla?

Tom


  reply	other threads:[~2010-01-05 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 14:50 simulator for sparc64? Joel Sherrill
2009-10-28 10:20 ` Doug Evans
2009-10-28 12:58   ` Joel Sherrill
2009-10-28 13:59     ` Jakob Engblom
2009-10-29  0:28       ` Joel Sherrill
2009-10-30 17:25       ` Python pretty printers and dynamic cast Elmenthaler, Jens
2009-10-30 17:51         ` Tom Tromey
2009-12-22  8:15           ` Elmenthaler, Jens
2010-01-05 15:34             ` Tom Tromey [this message]
2010-01-07  8:55               ` Elmenthaler, Jens

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=m3hbr0bm6k.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=jens.elmenthaler@verigy.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