comment on

I also found another way to do this without using FreezeThaw. Test::More also includes a function is_deeply that works about the same way:

is_deeply( \%crosslinks,
           \%crosslinkscorrect,
           "hash_comparison"
         );
[download]

This also much better for using in test scripts, since it returns more information when the test fails:

t/ReadCrossLinks....NOK 1#     Failed test (t/ReadCrossLinks.t at line
+ 32)
#     Structures begin differing at:
#          $got->{10.5.5.1}[0] = undef
#     $expected->{10.5.5.1}[0] = Does not exist
# Looks like you failed 1 tests of 1.
[download]

Not to mention the fact that since my app doesn't use FreezeThaw for anything else, I can remove that dependency from Makefile.PL. :-)

NOTE: The structures I will be comparing contain only scalars and anonymous refs. I have not tried is_deeply with refs as shown in perlfaq4, so I don't know if it acts more like cmpStr or cmpStrHard, but it works wonderfully for my purpose.

--J

In reply to Re: Using FreezeThaw correctly? by Rhys
in thread Using FreezeThaw correctly? by Rhys

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks