the former is also faster in that it's one less function call on the stack, but that's usually a secondary concern, if a concern at all.

Well, yes, usually the extra stack work wouldn't amount to much, unless/until the alias in question ends up getting called two million times on a given data set...

Wouldn't that be a fun and enlightening exercise in benchmarking? Someone uses the same module with the same test code on the same data set, but just switches between the "alias" name and the "real" name of the function, and gets to see the impact of the extra stack layer. (But I can imagine that some folks would feel like they had better things to do with their time.)

In reply to Re^2: Current en vogue technique for aliasing subs by graff
in thread Current en vogue technique for aliasing subs by thor

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.