Dear Dragonchild,

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:

%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 ; %%
Now, when I compile with Parse::Eyapp I have no conflicts

pl@nereida:~/LEyapp/examples$ eyapp -v dc2.eyp pl@nereida:~/LEyapp/examples$
I have written Parse::Eyapp that expands Parse::Yapp with capabilities similar to Parse::RecDescent. Consider using it.
Hope it will help

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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.