Thanks for your suggestions. I'll definitely be taking some of them on board. In regard to your comment about smart tokenising, I have a sort of negatively-matching lexer for that I call the antilexer which I might include but only if it survives as a sensible alternative after CPAN modules have been thorughly investigated.

For large continuous streams and such-like where I can't use the usual module, I use instance variables that have rules, recursion depths at which to start building trees, callback functions definable as "parser exits" (that's something I picked up from old prePerl technoliogy) to be invoked at certain points so that the tree never needs to be completed but can be acted on or code generated on the fly and I am sure there are other special needs situations I haven;t yet thought of!

It's a horrible minefield but I love it too ;);) after all - if the subject were reducible to bolting modules together and that working for every case, it wouldn't be so interesting, would it?

__________________________________________________________________________________

^M Free your mind!

In reply to Re^4: Writing Interpreters, Compilers and Translators in Perl by Moron
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.