Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Sérgio Durigan Júnior" <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Function-like cast notation support
Date: Wed, 17 Feb 2010 18:47:00 -0000	[thread overview]
Message-ID: <m3wrybg0n2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201002171345.36988.sergiodj@redhat.com> (=?utf-8?Q?=22S?=  =?utf-8?Q?=C3=A9rgio?= Durigan 	=?utf-8?Q?J=C3=BAnior=22's?= message of "Wed, 17 Feb 2010 13:45:29 -0200")

>>>>> "Sérgio" == Sérgio Durigan Júnior <sergiodj@redhat.com> writes:

Sérgio> The following patch adds support for function-like cast notation
Sérgio> on GDB.

This looks good.

It could use a NEWS entry.  I suggest waiting until my NEWS change goes
in, then adding it to the C++ improvements section.

Sérgio> Currently it only works for primitive data type (int,
Sérgio> char, double, etc), but I intend to send another patch soon that
Sérgio> will implement this feature for classes as well.

Hmm, you seem to have implemented this already...

Sérgio> +typebase_single
Sérgio>  	:	TYPENAME
Sérgio>  			{ $$ = $1.type; }

... because the lexer can return TYPENAME for a class name.

Sérgio> +		{ "void"      "void"		"'a'"		"void" }

I didn't realize this was supposed to work... learn something every day
:-)

This patch is ok.  Thanks.

For future reference, it is worth noting in the email how and whether
you regression tested it.  I assume that everybody does this, but it is
nice to be explicit about it.  At least in my case, this occasionally
helps me realize that I forgot.

Tom


  reply	other threads:[~2010-02-17 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 15:46 Sérgio Durigan Júnior
2010-02-17 18:47 ` Tom Tromey [this message]
2010-02-17 19:02   ` Sérgio Durigan Júnior

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=m3wrybg0n2.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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