If you're building an assembler, and the syntax is line based, you'll get a speed-up by parsing each line individually, rather than as one big file.
The reason is that P::RD performs the equivalent of:
s/^$syntax_I_recognize// && do { &Action_for_syntax };
And it does this for
everything, over and over again. This "nibbling" approach
is great for short strings, but for long strings, there's
a
whole lot of string copying going on.
theDamian said that a significant speedup would have been realized by changing these to:
/\G$syntax_I_recognize/gc && do { &Action_for_syntax };
and letting
pos() walk through the string, but alas never got the time to change P::RD into
Parse::FastDecent (this would have been the basic change).
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.