Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org,
	Daniel Jacobowitz <dan@codesourcery.com>,
	 Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH] [RFC] python: gdb.Type: strip typedefs past pointers too
Date: Mon, 20 Sep 2010 10:53:00 -0000	[thread overview]
Message-ID: <1284976091.1857.28.camel@localhost.localdomain> (raw)
In-Reply-To: <4C972A26.6040505@redhat.com>

On Mon, 2010-09-20 at 10:32 +0100, Phil Muldoon wrote:
> I think the current behaviour is correct.

Daniel took the time to explain that I basically tried to emulate what
looks to be a bug in the ptype command.

> Would you consider submitting it so that it
> can be turned on (off by default) via keyword?  (i.e. a recurse=True
> keyword).  That would allow us to preserve the existing functionality,
> but allow the user an API friendly way for this alternate recursive
> behaviour[.]

Any thoughts on Joel's question (sent a few days ago):
> (how about references?)
?


Paul Bolle


  reply	other threads:[~2010-09-20  9:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-18 14:12 Paul Bolle
2010-09-19 16:35 ` Joel Brobecker
2010-09-19 17:56   ` Paul Bolle
2010-09-20  9:32     ` Daniel Jacobowitz
2010-09-20  9:48       ` Paul Bolle
2010-09-20 10:04         ` Daniel Jacobowitz
2010-09-20 10:15 ` Phil Muldoon
2010-09-20 10:53   ` Paul Bolle [this message]
2010-09-20 12:02 ` Jan Kratochvil
2010-09-20 16:25   ` Paul Bolle
2010-09-20 13:59     ` Paul Bolle
2010-09-20 16:08     ` Paul Bolle
2010-09-21 12:39     ` Jan Kratochvil
2010-09-20 13:14 ` André Pönitz

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=1284976091.1857.28.camel@localhost.localdomain \
    --to=pebolle@tiscali.nl \
    --cc=brobecker@adacore.com \
    --cc=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@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