Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Keith Seitz'" <keiths@redhat.com>, <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFA] Token cleanup in c-exp.y
Date: Tue, 25 Aug 2009 13:45:00 -0000	[thread overview]
Message-ID: <000601ca2568$0eedea60$2cc9bf20$@u-strasbg.fr> (raw)
In-Reply-To: <4A9367B2.4040900@redhat.com>

   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?

The behavior of GDB did change indeed:
Old behavior:
(top-gdb) p current_objfile->*gdb_stderr
non-pointer-to-member value used in pointer-to-member construct
(top-gdb) p current_objfile-> *gdb_stderr
non-pointer-to-member value used in pointer-to-member construct

New behavior:
(top-gdb) p current_objfile->*gdb_stderr
non-pointer-to-member value used in pointer-to-member construct
(top-gdb) p current_objfile-> *gdb_stderr
A syntax error in expression, near `*gdb_stderr'.

  The problem is that I have 
no idea what it stands for...
and I never saw '->*' nor '.*' in any C sources.

  Please forgive the question if it is silly,
and remember that my knowledge of C is limited
to what I learned to be able to contribute to the GDB project...


Pierre Muller
Pascal language support maintainer for GDB




  reply	other threads:[~2009-08-25  9:40 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 [this message]
2009-08-25 14:10       ` Jiang Jilin
2009-08-25 15:11         ` Andreas Schwab
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='000601ca2568$0eedea60$2cc9bf20$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=keiths@redhat.com \
    --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