UPDATE: I may have misunderstood your post, and FIXED is meant as workaround.
> Fixed:
( foo {$Q} ) + foo {$t}
no, it's not, because this was what I expected.
> + is treated as the unary operator, so
And it would be binary
use strict;
use warnings;
sub foo (&){ shift->()}
sub baz (&){ shift->()}
sub bar {3}
my ($Q,$t,$res) = (10,3);
sub tst { ( foo {$Q} ) + baz {$t}; }
use B::Deparse;
print B::Deparse->new('-p')->coderef2text(\&tst);
print tst();
C:/Strawberry/perl/bin\perl.exe -w d:/tmp/pm/sym.pl
{
use warnings;
use strict;
(foo(sub {
$Q;
}
) + baz(sub {
$t;
}
));
}13
update
FWIW I chose + for an example which at least compiles b/c of the ambiguity.
I originally used / which fails without having any unary meaning (it's seen as the start of a m//)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|