Exactly right. Let me illustrate what is happening. Your data structure looks like (simplified):

$foo = { 'SOMETHING_01' => {'CLASS' => [ {'VALUE' => 'BUBBLE' } ] } }
Let's do a little analysis, assuming $foo retains its value:
$bar = $foo->{SOMETHING_01}; # $bar is hash reference $caz = %{$foo->{SOMETHING_01}; # $caz is a hash print $caz{'CLASS'}; # 'ARRAY(...)' - an array reference print $caz{'CLASS'}->[0]; # 'HASH(...)' - a hash reference
Note that when you copy a reference, you aren't copying the data -- you're making a new reference to the same data. By using the deep-copy method of the parent, you copy the data contained in the reference instead of the reference itself.

radiantmatrix
require General::Disclaimer;

In reply to Re^2: Forcing dereference by radiantmatrix
in thread Forcing dereference by blahblah

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.