yes, some globals are used, e.g. to construct the instruction words for the machine and keep track of address and lines, etc. these should not have any effect on the parsing, methinks. i've just made a reply, with some code and output samples, to revdiablo. as for startup cost, the beastie is _terribly_ slow. precompiling helps a bit, but what i'd really like to do is to get perlcc to be happy with it, but alas, that's a whole different can of worms: it has serious complaints and gives errors like "compile failed...that cannot happen!" :-/

In reply to Re: Re: Parse::RecDescent precompiled grammar != interp'd by bear_hwn
in thread Parse::RecDescent precompiled grammar != interp'd by bear_hwn

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.