I still don't get your code here: 
comparison: /(=[><]=)/ <commit> <error: Unable to match comparison, $1
+>
             | /=?[><]=?/
             | '='
             | '!='

[download]
If you did it the way I said, it's simpler and more direct: 
comparison: '<=' | '<' | '=' | '>=' | '>' | '!='

[download]
The matches are executed from left to right, so as long as you specify the longer match first, it does the right thing. Your code seems clumsy.

Also, I really don't see the need for those commits. Again, they clutter up the grammar. Have you tried removing them?

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

In reply to •Re: Solution: Parse::RecDescent and mini-language parsing by merlyn
in thread Parse::RecDescent and mini-language parsing by Flame

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.