When you pass an array as an argument to sub-routine it gets flattened. That is, as far as the sub-routine knows, its no longer an array, rather its now a list of its scalar elements. So shift will only get the first scalar in the array @_, not the entire list.

To illustrate: 

@foo = (1,2,3);
process_array(@foo);

sub process_array {
    # the special @_ variable now holds (1,2,3), NOT (@foo)
    $var1 = shift;    # $var1 will only get '1'.
    $var2 = shift;    # $var2 will only get '2'.
    $var3 = shift;    # $var3 will only get '3'.

}

[download]
To assign the entire argument list you would have to code the sub-routine like this: 
sub process_array {
    @args = @_;

}

[download]
or using an array reference: 
sub process_array {
    $args = \@_;

}

[download]
Hope that helps.

Amel - f.k.a. - kel

In reply to Re: Recieving lists as arguments by dsb
in thread Recieving lists as arguments by Amoe

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.