Hrm... yes... playing around some more I find the problem is more insidious than I had thought...

When I pass the following to it

{201({2}}
I get the error from the abstraction rule...
When I pass
4 * {201({2}}
My match fails, but I don't get the error from abstraction... maybe I am being bitten by leftop somehow...
Here follows the whole grammar.
startrule: { ($abscb,$self) = @arg } <reject> startrule: bin_op /^\Z/ { $item[1] } bin_op: logical_op # Lowest precendance the comparitive operators... logical_op: <leftop: equality_op LOGICAL equality_op> { treeify(@{$item[1]}); } equality_op: <leftop: comp_op EQUALITY comp_op> { treeify(@{$item[1]}); } comp_op: <leftop: add_op COMP add_op> { treeify(@{$item[1]}); } add_op: <leftop: prod_op SUM prod_op > { treeify(@{$item[1]}); } # Highest precendance. prod_op : <leftop: term PROD term > { treeify(@{$item[1]}); } SUM : '+' | '-' PROD : '*' | '/' | '%' COMP : />=?|<=?|le|ge|lt|gt/ EQUALITY : /!=|==?|eq|ne/ LOGICAL : 'AND' | 'OR' | '&&' | '||' arg_list: list_bin_op(s?) bin_op { [@{$item[1]},$item[2]] } # Functions, parenthesized equations, abstractions numbers and strin +gs are all basically atomic. term: function | abstraction | '(' <commit> bin_op ')' { $item[2] } | number | /\$[1-9]/ { [ 'arg', substr($item[1],1,1) ] } | string | 'NULL' | <error> abstraction: '{' number '(' <commit> arg_list ')' '}' { $abscb->($it +em[2],$item[4]) } | '{' <commit> number '}' { $abscb->($item[2]) } | <error?: GRRRRRRRRRRRR> <reject> # There is probably a prettier way to do these, but this works if: /if/i '(' list_bin_op(2) bin_op ')' { [$item[1],@{$item[3]},$ite +m[4]] } concat: /concat/i '(' list_bin_op(s) bin_op ')' { [$item[1],@{$item[ +3]},$item[4]] } left: /left/i '(' list_bin_op bin_op ')' { [@item[1,3,4]] } right: /right/i '(' list_bin_op bin_op ')' { [@item[1,3,4]] } ifnull: /ifnull/i '(' list_bin_op bin_op ')' { [@item[1,3,4]] } now: /now/i '(' ')' { [$item[1],''] } # if you don't return two item +s, they seem to get flattened somewhere, making it the string NOW length_func: /length/i '(' bin_op ')' { [@item[1,3]] } interval: /interval/i /\d+/ /MONTH|DAY|WEEK|YEAR/ { [@item[1,2,3]] } last_day: /last_day/i '(' bin_op ')' { [@item[1,3]] } date_format: /date_format/i '(' list_bin_op bin_op ')' { [@item[1,3 +,4]] } # just the list of all the functions function: if | concat | left | right | ifnull | now | length_func | +interval | last_day | date_format number: /[+-]?(?:\d+\.?\d*|\.\d+)/ { $item[1] } list_bin_op: bin_op ',' { $item[1] } string: <perl_quotelike> { if(!$item[1][0] && ($item[1][1] eq '"' || $item[1][1] eq "'")) { [$item[0],$item[1][2]]; } else { undef; } }

                - Ant
                - Some of my best work - (1 2 3)


In reply to Re^2: Forcing parse to fail in PArse::RecDescent by suaveant
in thread Forcing parse to fail in Parse::RecDescent by suaveant

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.