Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [RFC] python: gdb.Type: strip typedefs past pointers too
Date: Sun, 19 Sep 2010 16:35:00 -0000	[thread overview]
Message-ID: <20100918141253.GM3845@adacore.com> (raw)
In-Reply-To: <1284753356.21566.10.camel@localhost.localdomain>

> 1) I drafted a patch (pasted below this message) that works around this
> limitation:

Personally, I think that the current behavior is correct.  But I did
not participate in the design of the API, so others will probably
have a more informed opinion.

If we want to support the behavior you are looking for, I think it
should be done either through the control of a parameter (defaulted
to current behavior), or another method (recursive_strip_typedef).

> +  while (TYPE_CODE (real_type) == TYPE_CODE_PTR ||
> +	 TYPE_CODE (real_type) == TYPE_CODE_TYPEDEF)

Small nit on the coding style: the `||' should be at the beginning
of the next line:

        while (TYPE_CODE (real_type) == TYPE_CODE_PTR
               || TYPE_CODE (real_type) == TYPE_CODE_TYPEDEF)

(how about references?)

> +      if (TYPE_CODE (real_type) == TYPE_CODE_TYPEDEF)
> +	{
> +	  CHECK_TYPEDEF (real_type);
> +	}

When there is only one statement in the block, the prefered style
in GDB is to omit the curly braces:

      if (TYPE_CODE (real_type) == TYPE_CODE_TYPEDEF)
	CHECK_TYPEDEF (real_type);

-- 
Joel


  reply	other threads:[~2010-09-18 14:13 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 [this message]
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
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=20100918141253.GM3845@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pebolle@tiscali.nl \
    /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