Good Idea. It was the first thing I thought of too. Unfortunately, it does not work... The documentation clearly states that Parse::RecDescent does not opperate like yacc. The first successful match terminates the search. Yacc uses the "prefer the longest match" to choose which rule to fire if there are multiple rules that match the incomming string. So the way the rules are set up in the flex code that he got will cause lots of problems. See my post in the main thread as to why.
---
Crulx
crulx@iaxs.net

In reply to Re: (tye)Re: Flex, converting regexes, and other Interesting Stuff. by Crulx
in thread Flex, converting regexes, and other Interesting Stuff. by Petruchio

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.