In a recent post I noticed on_success => => sub { and thought, "huh, that's gotta hurt". To my surprise the extra => didn't have the effect I expected. I did a little experimenting:
use strict;
use warnings;
showParams(fat => => 'comma');
showParams('real', , 'comma');
showParams('explicit', undef, 'comma');
sub showParams {
my @params = @_;
for my $param (@params) {
if (!defined $param) {
print ">undef<\n";
next;
}
if (ref $param) {
print "'", ref $param, "'\n";
next;
}
print "'$param'\n";
}
printf "\n";
}
Prints:
'fat'
'comma'
'real'
'comma'
'explicit'
>undef<
'comma'
I expected to see the >undef< line for each version of the call to showParams. What am I missing?
perl -v reports: This is perl 5, version 32, subversion 1 (v5.32.1) built for MSWin32-x64-multi-thread.
Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
-
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.