Related articles |
---|
YACC with infinite lookahead daniele.benegiamo@aleph.it (Daniele Benegiamo) (1999-05-16) |
Re: YACC with infinite lookahead bbuckley@ozemail.com.au (Bob Buckley) (1999-05-20) |
Re: YACC with infinite lookahead cfc@world.std.com (Chris F Clark) (1999-05-20) |
Re:YACC with infinite lookahead scavadini@hotmail.com (Salvador V. Cavadini) (1999-05-20) |
Re: YACC with infinite lookahead demaille@solo.enst.fr (Akim Demaille) (1999-05-21) |
Re: YACC with infinite lookahead vmakarov@cygnus.com (Vladimir Makarov) (1999-05-21) |
Re: YACC with infinite lookahead bromage@cs.mu.OZ.AU (1999-05-27) |
From: | bromage@cs.mu.OZ.AU (Andrew Bromage) |
Newsgroups: | comp.compilers |
Date: | 27 May 1999 23:21:23 -0400 |
Organization: | Computer Science, The University of Melbourne |
References: | 99-05-072 99-05-095 |
Keywords: | parse, yacc, C++ |
G'day all.
Akim Demaille <demaille@solo.enst.fr> writes:
>What exactly are the problems given to LALR(1) by C++?
The biggie is the famous rule of C++ grammar which goes something like
this:
If it looks like a declaration, then it is.
Otherwise, if it looks like a statement, then it is.
Otherwise, it's a syntax error.
Naturally, such a rule would only be needed if the rules for
declarations and statements are so ambiguously overlapped that the
usual arsenal of lexical feedback hacks won't work.
Cheers,
Andrew Bromage
Return to the
comp.compilers page.
Search the
comp.compilers archives again.