UPDATE:

I've generated precompiled versions of both grammars from each environment. I'm assuming (have not checked yet) that Precompile and new generate identical grammar objects. (If someone more familiar with the internals knows whether this assumption holds, I'd be glad to know for certain before digging through the code myself.) The code being generated is identical in both cases--as I expected.

The place where the differences I can detect appear to come in when the magic $& variable is used to examine the last match. The first disparity in trace output happens in this section of code:

unless ($text =~ s/\A($skip)/$lastsep=$1 and ""/e and $text =~ s/\A( +?:[a-z_][a-z0-9_]*)//i) { $expectation->failed(); Parse::RecDescent::_trace(q{<<Didn't match terminal>>}, Parse::RecDescent::_tracefirst($text)) if defined $::RD_TRACE; last; } Parse::RecDescent::_trace( q{>>Matched terminal<< (return value: [} . $& . q{])}, Parse::RecDescent::_tracefirst($text)) if defined $::RD_TRACE; push @item, $item{__PATTERN1__}=$&;

As far as I can tell by reading the code, the value in $& is being lost somewhere between the unless and the _trace.

Anyway, still searching...


In reply to Re: Where to find the source of this Parse::RecDescent oddness? by hanenkamp
in thread Where to find the source of this Parse::RecDescent oddness? by hanenkamp

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.