Interesting, I never thought of that method to figure out the arguments. But you're right, forcing the 1st argument into a reference breaks too many usual idioms (such as trim(<STDIN>) as you mentioned).

I wish that "@_" was undef when a function is called with no arguments (as opposed to called with an empty array). Or, that there was some other way to detect no arguments without forcing the 1st argument into a reference.

I appreciate the "spoiler". I'll add it to my perl KB (even if I never use it).

- Wyrd

In reply to Re^2: Is silent use of $_ for empty argument lists reasonable for "shortcut" functions? (E2CUTE) by Wyrdweaver
in thread Is silent use of $_ for empty argument lists reasonable for "shortcut" functions? by Wyrdweaver

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.