ALTS, monks!

I'm having a little problem using FreezeThaw to compare two hashes. The hashes are fairly complex (hash of lists of hashes). According to perlfaq4, I ought to be able to do this in a test file: 

use FreezeThaw qw(cmpStrHard);
use JScan::ReadCrossLinks;
use Test::More;
BEGIN { plan tests => 1, todo => [1] };

# Initialize %crosslinkscorrect with what we expect.

##################################################
# Test 1.  Read our test file and compare to the control.
ReadCrossLinks(\%crosslinks, \%options);

# This should fail if the hashes are different, right?
ok(cmpStrHard(\%crosslinks, \%crosslinkscorrect));

[download]

So the problem is that this test always succeeds, even when I feed it mangled data. What gives? Alternatively, is there another, simpler way to compare the contents of two hashes that contain complex data like this?

--J

In reply to Using FreezeThaw correctly? by Rhys

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.