I've made this library, called Tie::MorphHash, to use @ISA polymorphism on package global hashes (of hashes, etc) using tie(). It works great until you have 3 levels of @ISA inheritance. At that point, this breaks: 
use Data::Dumper qw(Dumper);
print Dumper $cc::zz{key1}{subkey1};

[download]
but this doesn't: 
use Data::Dumper qw(Dumper);
my $key1 = $cc::zz{key1};
print Dumper $key1->{subkey1};

[download]
I've boiled the problem down as much as I can. To get the whole source for the example, download:

http://unlox775.8m.com/morphhash_error.tgz

This is quite a doosey to debug. I've left a buncha debug in the Tie::MorphHash library, you just need to set $Tie::MorphHash::debug to 1 and it will tell you about All Tiehash related events and details. It's pretty verbose...

Thank you, Thank you, Thank you if you can figure out a decent way around this!

In reply to Recursive tied hash crap out by unlox775_0

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.