I, too, dislike having bunches of curly brackets cluttering up my code.
However, the
func({ key1 => 'value1', key2 => 'etc', });
invocation style for named arguments has a benefit I consider very valuable: if an invocation is malformed, a warning is issued at the point of invocation.
In the alternate, arguably cleaner, invocation style that does not use an anonymous hash, the warning is issued at a point within the called function, so the question immediately becomes "Where was this function invoked, so I can go there and fix the improperly specified arguments".
use warnings;
use strict;
func_1({ one => 'uno', two => 'dos', three => }); # <-- line 38
func_2(one => 'uno', two => 'dos', three => );
sub func_1 {
my %args = %{ $_[0] };
print "func_1: one translates to $args{one} \n";
}
sub func_2 {
my %args = @_; # <-- line 48
print "func_2: one translates to $args{one} \n";
}
Output:
>perl 765727_1.pl
Odd number of elements in anonymous hash at 765727_1.pl line 38.
func_1: one translates to uno
Odd number of elements in hash assignment at 765727_1.pl line 48.
func_2: one translates to uno
-
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.