In add to pjf answer I want to point that if you want to return at least 2 lists (arrays or hashes) it's better to return references, because 
return (@a,@b)

[download]
should push @a and @b in a list, and then return this list. It is not possible to separate them.

It's better to code: 
return (\@a,\@b);

[download]
and then receive the arrays as references 
($ra,$rb)=myfunc();

[download]
See perldoc perlref for more details
I want to point also that returning a referece is faster and cheaper (in terms of CPU and memory), but better is not the best word we can use, it depends of the problem (See this node written by merlyn)

Hope this help
Hopes

Thanks to graq for the information about the typo in my code

In reply to Re: Advantages to returning array vs. reference by hopes
in thread Advantages to returning array vs. reference by melguin

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.