I am willing to make several bets.

First of all, that the experience of having tried to do it with Parse::RecDescent made the rewrite easier to do.

Secondly I'll bet that if Parse::RecDescent used /\G.../gc matches to tokenize rather than nibbling strings, its performance would have been good enough. Maybe not as good as your final version, but good enough to make do.

Thirdly I'll bet that there are more Perl programmers who are inclined to not use modules that would have helped than there are Perl programmers who are inclined to use modules that are not worthwhile. (Though it is certainly possible to err both ways.)

In reply to Re: On modules by tilly
in thread On modules by samizdat

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.