Related articles |
---|
How to resolve ambiguity? idht@yahoo.com (2003-12-27) |
Re: How to resolve ambiguity? snicol@apk.net (Scott Nicol) (2004-01-02) |
Re: How to resolve ambiguity? derkgwen@HotPOP.com (Derk Gwen) (2004-01-02) |
Re: How to resolve ambiguity? snicol@apk.net (Scott Nicol) (2004-01-02) |
From: | Scott Nicol <snicol@apk.net> |
Newsgroups: | comp.compilers |
Date: | 2 Jan 2004 03:40:50 -0500 |
Organization: | APK Net |
References: | 03-12-143 |
Keywords: | parse |
Posted-Date: | 02 Jan 2004 03:40:50 EST |
On 27 Dec 2003 15:02:36 -0500, idht@yahoo.com (Igor) wrote:
><struct-type> ::= <type-name>
Another (simpler) alternative is to have the lexer return different
terminals for each type, i.e. struct-type-name, class-type-name, etc.
This still leaves you with the shift/reduce caused by the array-type
rule, which needs to be move up to the "type" rule.
--
Scott Nicol
snicol@apk.net
Return to the
comp.compilers page.
Search the
comp.compilers archives again.