Here's a straightforward approach:

for my $k1 ( keys %foo ) { next if not defined $bar{ $k1 }; for my $k2 ( keys %{ $foo{ $k1 } } ) { next if not defined $bar{ $k1 }{ $k2 }; dance() if $foo{ $k1 }{ $k2 } eq $bar{ $k1 }{ $k2 }; } }
If the number of keys in one hash is much greater than the number of keys in the other, it may pay to optimize this search so that the iteration happens over the keys of the hash with fewer keys.

I show a slightly "fancier" approach below, because I think you may find it instructive, but IMO the first approach is far preferable for production code:

for my $k1 ( grep defined $h2{ $_ }, keys %h1 ) { for my $k2 ( grep defined $h2{ $k1 }{ $_ }, keys %{ $h1{ $k1 } } ) { dance() if $h1{ $k1 }{ $k2 } eq $h2{ $k1 }{ $k2 }; } }

the lowliest monk


In reply to Re: what's the best way to compare two 2D hashes? by tlm
in thread what's the best way to compare two 2D hashes? by coontie

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.