You might want to read the GOTCHAs section of Parse::Recdescent too. It has a formula for guaranteeing that either the whole thing parses, or nothing at all parses--assuming that the input string should be completely parsed. Anyway, if added to your code, you could add these two productions like this so that where is the new toplevel production:

where : condition eofile
eofile : /^\Z/

[download]

If you don't need to parse the whole input, you could make eofile an appropriate end marker for the parsed input. Adding <error> directives in the right places in your other productions may also help.

In reply to Re: Converting BNF for use in Parse::RecDescent by hanenkamp
in thread Converting BNF for use in Parse::RecDescent by Anonymous Monk

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.