I have seen two different methods of assigning my-type variables from passed in arguments. The two ways I am talking about is shown below:
sub routine1 {
    my ($var_one, $var_two, $var_three) = @_;
    ...
}

sub routine2{
    my $var_one = shift;
    my $var_two = shift;
    my $var_three = shift;
    ...
}

[download]

So, my question is "What are the benefits, drawbacks relating to performance of the two ways, if any?" I know that shift reduces the array by one, and then the leftovers are typically used in loops, etc... I have not been able to see anything that explains any other difference, so are the two methods relatively equal in execution time, and therefore the ultimate decision is preference of the coder?

the_Don
...making offers others can't rufuse.

In reply to Argument Passing, preference or performance ? by the_Don

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.