You have to test that you have the correct number of arguments anyway (in most cases, at least).
But this is really about parameter validation: required versus optional parameters, acceptable ranges of parameter values, misspelled parameter names, etc. Depending on the situation, validation can be quite simple (or non-existent!) or quite involved. In any case, it is something that can only be handled 'within the function'.

But again, to me, the question of whether each named parameter has some value associated with it is a question that can be (and is best) handled by default, right there and then at the function call.

Also: specific error messages are way better than generic ones.
I tend to agree, but this becomes a matter of individual taste. For myself, a message like  Odd number of elements in anonymous hash at 765727_1.pl line 38. is both sufficiently specific and sufficiently proximate to the point of occurrence – especially if the program died at line 38!

In reply to Re^5: 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.