When matching terminals, Parse::RecDescent seems to produce a match if a token begins with the terminal, rather than trying for an exact match. This code demonstrates this:

#!/usr/bin/perl use warnings; use strict; use Parse::RecDescent; my $grammar = q{ FOO: "foo" }; my $p = Parse::RecDescent->new($grammar); my @tests = ("foo", "foo ", "foo bar", "football", "fog", "barfoo", "b +ar foo"); for my $test (@tests) { if (my $ret = $p->FOO($test)) { print "match: '$test' -> '$ret'\n"; } else { print "no match: '$test'\n"; } }

This isn't what I want. I want it to produce an error/return undef when what was entered doesn't match in full, rather than simply eating the remainder.

I doubt this is a bug, because it seems too trivial, so I suspect that this is actually a lack of understanding of parsing in general on my part. Could someone please set me straight here? Thanks!


In reply to Matching terminals with Parse::RecDescent by fce2

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.