You *can* do that, but then end up copying a bunch of memory around, whereas when you use a reference you're just copying, well, the reference. So personally I think it's generally better to just use references as arguments. It's faster.

In addition, what if you later decided that you needed to call the subroutine with two hash arguments instead of just one? Now you've got a problem, because you can't say:

foo(%bar, %baz);
because the hashes get flattened into a list (as all subroutine arguments do). So instead you've got to pass in references to the hashes, and now you'll have to change all mentions of the hash inside the subroutine to use the reference instead.

So it'll save you possible future work to use references.


In reply to RE: Re: passing hashes to a function by btrott
in thread passing hashes to a function by skazat

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.