My Goal: Use a sub to manipulate multiple large blocks of text without making copies of the original text.

What I think I know:

1.Stick with references as Scalars are passed by reference and can be accessed via $_[0], $_[1], etc.
2.Creating a scalar variable within the sub makes a copy of the scalar.

My problem: (Besides being new to perl)

When multiple scalars are passed, the code gets harder to read and understand.
So, I'd like to use named variables.

A solution Use more references in the sub. 
sub processText($$) {
  my $subParm0ref = \$_[0];
  my $subParm1ref = \$_[1];
  
  # Do something ....

  print $$subParm0ref;
  print $$subParm1ref;
}

[download]
My Questions:

Is this a good way to handle the problem?

Is there a better way or am I missing something here?

In reply to Memory Use and/or efficiency passing scalars to subs by knexus

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.