As a former Perl newbie, I'd suggest avoiding string literals as hash keys. One typo can take you hours to find, because the "uninitialized value" line number will be where you try to use it, and not where you typoed. 

my $LB = 'LB';
my $LENGTH_RANGES = 'LENGTH_RANGES';
my $WIDTH_RANGES = 'WIDTH_RANGES';
my $EM_POLY = 'EM_POLY';

# ...sometime later...
$metals{$LB}{$LENGTH_RANGES} = [ 0, 10 ];
$metals{$LB}{$WIDTH_RANGES} = [ 0, 1.080 ];
$metals{$LB}{$EM_POLY} = "(-0.665364 + (9.6216 * W))*(10/L)";

[download]

Then Perl will check your spelling on the variable names (which are really constants, but that's another kettle of fish).

But as hdb said, Data::Dumper is invaluable in this area.

-QM
--
Quantum Mechanics: The dreams stuff is made of

In reply to Re: Multidimentional hash by QM
in thread Multidimentional hash by freekngeek

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.