Re: Oracle grammar ambiguities and conflicts

>At a syntax error we check whether the current token is a keyword.
>If an identifier token would be acceptable at this location then
>we convert the keyword token into an identifier token and continue parsing.


I also use this technique to handle typedef in C. SLK facilitates this with
the following retry rules on return from the user error routine:


If the same token is returned, the algorithm proceeds as if nothing
happened. The parse stack is popped. For mismatch(), this is one way to
insert a missing token.


If a different token is returned, the algorithm does a retry using the new
token and the same nonterminal.


If zero is returned, the algorithm retries using the old token/nonterminal
pair. This is useful when the action required is to change the symbol table
information.


The SLK parser generator: http://home.earthlink.net/~slkpg/

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