Re: shift-reduce conflict,

"Thinh T. Nguyen" <ttnguyen@eecs.uic.edu> writes:


> I am writing a parser file (input to bison) for a toy JAVA compiler and
> am running into a shift-reduce conflict that could not be resolved. The
> problem involves
>
> <cast-expression> -> '(' <type> ')' <expression>
>
> where <type> could be any ID. The problem arises when bison parses
> something like '(string)' and confuses whether to reduce it to an
> expression or keep on parsing because it could be a cast-expression.


Can you make Bison happy by allowing


        '(' <expression> ')' <expression>


as legal syntax, and then requiring that the prefix-expression denote
a type? Off the top of my head, this should be OK, shouldn't make
error reporting any more confusing, and even allows for future expansion
of the language in the direction of type-expressions :-)
--


--

Return to the comp.compilers page.
Search the comp.compilers archives again.