TheoPeterson is right, but he overlooks something:

my %hash; my %direc; my $record = { DIR => 3 }; $hash{'myhash'} = $record; $direc{'this'} = "something"; $direc{'that'} = "another"; #Here we swat the previous value of $hash{'myhash'} #the previous value of $hash{myhash} ($record) vanishes $hash{'myhash'}{ODIR} = \%direc; print $hash{'myhash'}->{ODIR}{'this'},"\n"; print $hash{'myhash'}{ODIR}{'this'},"\n"; print $hash{'myhash'},"\n";

In general, don't bother dereferencing with ->. It's not worth it unless you know why you want to.

Also, you don't need the '' around the key values. They'll just cause you trouble later.

____________________
Jeremy
I didn't believe in evil until I dated it.


In reply to Re: Referencing to a hash inside a hash of hashes. by jepri
in thread Referencing to a hash inside a hash of hashes. by JPaul

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.