The normal approach, irrespective of scope, is to have a single copy of the string and pass scalar references around. For example:
my $bigref = bigget; ... do something ... do_something_more( $bigref ); sub bigget { local $/ = undef(); # disable carriage control locally open my $fh, $ENV{BIG_STUFF} or die "$!: \$ENV{BIG_STUFF}\n"; my $slurp = <$fh>; close $fh; \$slurp; # return the reference to $slurp, which also keeps it ali +ve outside this scope!!! } sub do_something_more { my $bigref = shift; # copying the ref not the string $$bigref =~ /^\s+(\S+)/; # using a dereference my $first_word = $1; ... do more ... }

One world, one people


In reply to Re: Whats quicker - passing along as variable to sub, or global var? by anonymized user 468275
in thread Whats quicker - passing along as variable to sub, or global var? by ultranerds

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.