Well, I'm not sure why you'd want to do that. For one, you now have nested subroutines with the ol' "Value won't stay shared" in the middle to boot. If you control the call to your subroutine, you can require they pass it by reference as the first parameter. If you don't, wrapper it up in a helper routine: 
sub routine_that_they_call {
  my @args = @_;
  my %data_to_be_filled;
  recursive_subroutine(\%data_to_be_filled, @args);
  return \%data_to_be_filled;
}

[download]
Now you don't have to define a nested subroutine.

-- Randal L. Schwartz, Perl hacker

In reply to RE: RE: RE: RE: Hash Push by merlyn
in thread Hash Push by Adam

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.