That was my first idea too ...

... but I think something is fundamentally broken with the parsing of prototyped sub calls.

see how + fails ... 

lanx@lanx-1005HA:/tmp$ perl -MO=Deparse -e 'sub foo (&) {}; foo {"foo"
+} + 3'
Too many arguments for main::foo at -e line 1, at EOF
-e had compilation errors.
sub foo (&) {
    
}
&foo(sub {
    'foo';
}
, 3);

[download]
... while . works 
lanx@lanx-1005HA:/tmp$ perl -MO=Deparse -e 'sub foo (&) {}; foo {"foo"
+} . "3"'
sub foo (&) {
    
}
foo(sub {
    'foo';
}
) . '3';
-e syntax OK

[download]

Seems like the parser tries to guess if a second parameter follows even if no further parameters are allowed.

The + fails because it's also a unary operator, so the foo( BLOCK, +3 ) interpretation is preferred, but later rejected, without backtracking into another, binary interpretation.

I'm no expert of how the lexer works but implementing parsing on such heuristics is a fragile thing.

Hopefully this can be fixed in the future.

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

update

that's really a depressing bug, I had much hope in using more block prototypes.

In reply to Re^2: BUG when parsing defined-or? (calls of prototyped subs) by LanX
in thread BUG when parsing defined-or ? by LanX

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.