There are two ways of passing data to a subroutine:

- call by value
- call by reference

References are always a good idea - especially if you have large or complex datastructures, but using values is much easier in the beginning. Here's an example that I've posted earlier this day on a german perl-community site. Two array-references gets passed to a function in an anonymous hash: 

#!/usr/bin/perl

use strict;
use warnings;

use Data::Dumper;

my @numbers = (1..10);
my @words = qw(hello world outside);

function( {NUMBERS=>\@numbers , WORDS=>\@words} );
exit;

sub function {
  die "no parameter!\n" unless @_;
  my %opt = %{ shift @_ };
  print Dumper \%opt;

  my @i_words = $opt{WORDS};
  print Dumper \@i_words;

  my @i_numbers = $opt{NUMBERS};
  print Dumper \@i_numbers;
}

[download]

In reply to Re: passing arrays to subroutines by neniro
in thread passing arrays to subroutines 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.