Neat solution.

I was going to say that they always come out in the same order because the hashing key does not change. Unfortunately that did not stand up to testing. The order the elements are inserted into the hash makes a difference: 

my ( %hash1, %hash2 );
$hash1{"value$_"} = $_ for ( 1 .. 11 );
$hash2{"value$_"} = $_ for ( 5 .. 11 );
$hash2{"value$_"} = $_ for ( 1 .. 4 );

sub flatten { return "@_" }

if ( flatten(%hash1) eq flatten(%hash2) ) {
        print "equal\n". flatten( %hash1 ) . "\n" . flatten(%hash2)
} else {
        print "not\n" . flatten( %hash1 ) . "\n" . flatten(%hash2);
}


not
value10 10 value11 11 value1 1 value2 2 value3 3 value4 4 value5 5 val
+ue6 6 value7 7 value8 8 value9 9
value10 10 value1 1 value11 11 value2 2 value3 3 value4 4 value5 5 val
+ue6 6 value7 7 value8 8 value9 9
========== [C:\users\jake\code\komodo\test3.pl] run finished. ========
+==

[download]
So flatten needs to be: 
sub flatten {
  my %hash = @_; 
  return join '', map "$hash{$_}$_", sort keys %hash;
}

[download]

The answer to your question on how not to use a sub would be to use the join, map in the if clause. This saves passing the hash by value, but duplicates the logic on either side of the eq

-- iakobski

In reply to Re: andye Re: How to test equality of hashes? by iakobski
in thread How to test equality of hashes? by acser

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.