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";
    }

[download]
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

[download]

In reply to Re: Preferred technique for named subroutine parameters? by AnomalousMonk
in thread Preferred technique for named subroutine parameters? by Anonymous Monk

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.