From: Kyuupi <kyuupichan@gmail.com>
To: "Joseph S. Myers" <jsm@polyomino.org.uk>
Cc: Zack Weinberg <zack@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: New C parser [patch]
Date: Tue, 26 Oct 2004 12:21:00 -0000 [thread overview]
Message-ID: <2116058a04102604421a21c068@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410260008550.11937@digraph.polyomino.org.uk>
On Tue, 26 Oct 2004 00:37:21 +0000 (UTC), Joseph S. Myers
<jsm@polyomino.org.uk> wrote:
> On Mon, 25 Oct 2004, Zack Weinberg wrote:
>
> > I'm generally quite happy with this patch. Could you enumerate all
> > the places where 2-token lookahead is needed, and give an opinion as
> > to how many of those could be eliminated through future cleanups?
>
> Distinguishing array declarators [*] and [*foo].
>
> Distinguishing whether an identifier where a statement is expected is a
> label or starts an expression.
Those are the only two in standard C that I don't believe can be
reasonably avoided in a recursive descent parser.
> Distinguishing whether '(' in an expression starts a parenthesised
> subexpression, a statement expression or is followed by a type name.
> (Also after sizeof and alignof.)
This wasn't necessary in the parser I have written.
> Distinguishing whether an identifier in an expression is followed by '('
> and so could be an implicit function declaration.
I don't believe this is either.
Neil.
next prev parent reply other threads:[~2004-10-26 11:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 1:25 Joseph S. Myers
2004-10-23 2:39 ` Steven Bosscher
2004-10-23 4:15 ` Joseph S. Myers
2004-10-23 5:44 ` Scott Robert Ladd
2004-10-24 22:49 ` Joseph S. Myers
2004-10-26 0:32 ` Zack Weinberg
2004-10-26 1:03 ` Andrew Pinski
2004-10-26 1:03 ` Zack Weinberg
2004-10-26 1:11 ` Joseph S. Myers
2004-10-26 8:23 ` Zack Weinberg
2004-10-26 1:30 ` Gabriel Dos Reis
2004-10-26 1:06 ` Joseph S. Myers
2004-10-26 2:47 ` Joseph S. Myers
2004-10-26 3:48 ` Mark Mitchell
2004-10-26 12:21 ` Kyuupi [this message]
2004-10-26 12:32 ` Joseph S. Myers
2004-10-26 11:42 ` Joseph S. Myers
2004-10-27 19:04 ` Richard Henderson
2004-10-27 19:11 ` Richard Guenther
2004-10-27 19:41 ` Zack Weinberg
2004-10-27 19:31 ` Zack Weinberg
2004-10-27 21:31 ` Richard Henderson
2004-10-28 7:38 ` Alan Modra
2004-10-27 20:25 ` Joseph S. Myers
2004-10-25 22:33 ` Ziemowit Laski
2004-10-25 22:51 ` Joseph S. Myers
2004-10-25 23:45 ` Ziemowit Laski
2004-10-25 23:53 ` Scott Robert Ladd
2004-10-26 0:03 ` Unified front end for C and C++ (was Re: New C parser [patch]) Matt Austern
2004-10-26 1:26 ` Scott Robert Ladd
2004-10-26 1:43 ` Gabriel Dos Reis
2004-10-26 2:01 ` Scott Robert Ladd
2004-10-26 15:38 ` Gabriel Dos Reis
2004-10-26 0:28 ` New C parser [patch] Ziemowit Laski
2004-10-26 1:20 ` Scott Robert Ladd
2004-10-26 6:08 ` Unified C and C++ front end (was Re: New C parser [patch]) Matt Austern
2004-10-26 11:14 ` Joseph S. Myers
2004-10-26 16:04 ` Gabriel Dos Reis
2004-10-26 16:51 ` Joseph S. Myers
2004-10-26 0:37 ` New C parser [patch] Joseph S. Myers
2004-10-26 0:03 ` Stan Shebs
2004-10-26 1:46 ` Gabriel Dos Reis
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=2116058a04102604421a21c068@mail.gmail.com \
--to=kyuupichan@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jsm@polyomino.org.uk \
--cc=zack@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).