Maybe, maybe not. Sometimes, it's rather obvious what the arguments are. Sometimes, all the arguments play the same role. And sometimes, it would be just bloody annoying to use named parameters all the time. Do you really want to write: 
    my $substr = substr(subject => $str, first_char => 5, length => 3,
+ replacement => "bar");
    my @parts = split(subject => $str, pattern => qr/foo/, max_parts =
+> 7, keep_trailing_empty_fields => 1);

[download]
? I'm not sure whether it's more readable. Or whether it's harder to remember that a negative third argument to split indicates trailing empty fields should be preserved than it is to remember the name of the flag.

In reply to Re^4: Correct idiom for default parameters by JavaFan
in thread Correct idiom for default parameters by mrider

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.