Because here's my real problem: 

sub genHash {
    my $hashn = shift;
    return "\%$hashn = (\n" . join(",\n", 
    map {
        $key = $_;
        "'$key' => " . 
        (ref $$hashn{$_} ? 
            '{' . join(",\n", map {
                "'$_' => qq~" . safeTilde($$hashn{$key}->{$_}) . '~'
            } keys %{$$hashn{$key}}) . '}'
        :
            'qq~' . safeTilde($$hashn{$key}) . '~'
        )
    } keys %$hashn) . ");\n";
}


sub safeTilde {
    my $code = shift;
    $code =~ s/\~/\\~/g;
    return $code;
}

[download]
then you would call it by genHash(\%somehash)

though it does work, it's just is a little long and messy..

Oh, by the way, it takes a hash and generates the perl to re-create it :)

Edit kudra, 2002-05-27 s/pre/code

In reply to Re: Re: map and each? by L0rdPhi1
in thread map and each? by L0rdPhi1

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.