If I was to use Parse::RecDescent, would it go faster?

Parse::RecDescent is known to be slow. So much so that Damian Conway want(?:ed|s) to write Parse::RecDescent::Fast. Or something like that.

Another alternative is to use Parse::Yapp (Yet Another Perl Parser). I haven't used it personally, but a number of people who have have appreciated the speed. They have also appreciated less, the fact that it is drop-in compatible with yacc(1). No-one knows yacc anymore. stefp was threatening a while back to write a front-end to P::Y to get it to accept P::RD's input, but I don't know if he got round to doing so.

- another intruder with the mooring in the heart of the Perl

In reply to Re: Parse::RecDescent and need for speed (eq Parse::Yapp) by grinder
in thread Parse::RecDescent and need for speed by EchoAngel

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.