|Ambiguities from Special-Case Productions firstname.lastname@example.org (Evangelos Drikos) (2005-09-14)|
|Re: Ambiguities from Special-Case Productions email@example.com (Cleo Saulnier) (2005-09-15)|
|Re: Ambiguities from Special-Case Productions firstname.lastname@example.org (Ivan Boldyrev) (2005-09-17)|
|Re: Ambiguities from Special-Case Productions DrDiettrich@compuserve.de (Hans-Peter Diettrich) (2005-09-17)|
|Re: Ambiguities from Special-Case Productions email@example.com (Evangelos Drikos) (2005-09-22)|
|From:||Ivan Boldyrev <firstname.lastname@example.org>|
|Date:||17 Sep 2005 13:54:08 -0400|
|Organization:||this field is intentionally left blank|
|Posted-Date:||17 Sep 2005 13:54:08 EDT|
|X-Greenpeace:||No animals were harmed in this message|
On 9233 day of my life Evangelos Drikos wrote:
> Any references of how such ambiguities are handled in a GLR or is it a
> simple & usual case for such a parser?
GLR is like LR parser that doesn't signal na error when ambiguity is
found, but explores all alternatives.
Naive GLR parser will return all possible interpretations; more
sophisticated one might ignore some alternatives if progammer provide
Some LR parser (yacc and GNU Bison, for example) also can resolve
ambiguities when programmers tells how to do it.
Return to the
Search the comp.compilers archives again.