...More thoughts...

There is a new edition of the book by Grune et al Parsing Techniques. It should be out or close.

Often people think about LR or LL parsing but the first edition of "Parsing Techniques" talks about starting anywhere! which is interesting at least in the sense of having maybe two-staged tokenizing <chess>?!</chess>

then there is HOP::Lexer. I haven't played much but it is quite slower than anything based on Parse::Yapp. Still a mixed approach could be nice...

finally using 5.9.x or more one can plug a different regexp engine, say a small one that permits "streaming"

Update: [SDF] seems also interesting.

cheers --stephan

In reply to Re^5: Writing Interpreters, Compilers and Translators in Perl by sgt
in thread Writing Interpreters, Compilers and Translators in Perl by Moron

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.