Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@redhat.com>
To: Jiang Jilin <freephp@gmail.com>
Cc: Pierre Muller <muller@ics.u-strasbg.fr>,
	Keith Seitz <keiths@redhat.com>,
	        tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFA] Token cleanup in c-exp.y
Date: Tue, 25 Aug 2009 15:11:00 -0000	[thread overview]
Message-ID: <m3skfgm0yf.fsf@hase.home> (raw)
In-Reply-To: <7d77a27d0908250645t7b2c4465y2276c951ae296da4@mail.gmail.com> 	(Jiang Jilin's message of "Tue, 25 Aug 2009 21:45:05 +0800")

Jiang Jilin <freephp@gmail.com> writes:

> On Tue, Aug 25, 2009 at 5:40 PM, Pierre Muller<muller@ics.u-strasbg.fr> wrote:
>>   Just for information:
>> doesn't this mean that
>> the parser that previously accepted
>>  '->  *' with spaces between the arrow and the star,
>> will now reject such patterns?
>>  Is this also what a C compile would do?
>
> Personally, I think  '->*' is _not_  really a single token or
> operation like '++' in ISO C Standard, so the patch is _not_ correct.

In C++ both `.*' and `->*' are single tokens.  In C, in a valid
expression, `*' can never follow `.' or `->'.

Andreas.

-- 
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84  5EC7 45C6 250E 6F00 984E
"And now for something completely different."


  reply	other threads:[~2009-08-25 14:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24 23:06 Keith Seitz
2009-08-24 23:08 ` Tom Tromey
2009-08-25  5:03   ` Keith Seitz
2009-08-25 13:45     ` Pierre Muller
2009-08-25 14:10       ` Jiang Jilin
2009-08-25 15:11         ` Andreas Schwab [this message]
2009-08-25 15:28 ` Matt Rice
2009-08-25 15:46   ` Tom Tromey
2009-08-25 15:47 ` Tom Tromey
2009-08-25 18:07   ` Keith Seitz
2009-08-25 18:41     ` Tom Tromey
2009-08-25 18:42       ` Keith Seitz

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=m3skfgm0yf.fsf@hase.home \
    --to=schwab@redhat.com \
    --cc=freephp@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=muller@ics.u-strasbg.fr \
    --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