An alternative subject to your design constraints (no expanding) is to move the conflict from reduce-reduce to shift-reduce and solve it using priorities:
Now, when I compile with Parse::Eyapp I have no conflicts%start column_ident %left DUMMY %right '.' %% column_ident: table_ident '.' ident | table_ident ; table_ident: ident '.' database_ident | ident %prec DUMMY ; database_ident: ident ; ident: IDENT | IDENT_QUOTED ; %%
I have written Parse::Eyapp that expands Parse::Yapp with capabilities similar to Parse::RecDescent. Consider using it.pl@nereida:~/LEyapp/examples$ eyapp -v dc2.eyp pl@nereida:~/LEyapp/examples$
Best
Casiano
In reply to Re: (OT) Yapp rules and resolving reduce/reduce errors
by casiano
in thread (OT) Yapp rules and resolving reduce/reduce errors
by dragonchild
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |