comment on

If its just a few keys that get the most usage, and sometimes get misspelled, you could consider using constants for the keys. that way, perl -c will catch and typos in the constant names. For instance:

use constant FIRST_NAME => "first_name";
use constant LAST_NAME => "last_name";

my %some_hash = (
   FIRST_NAME() => "john",
   LAST_NAME()  => "doe",
);

my $f_name = $some_hash{FRIST_NAME()}; # caught by perl -c
my $f_name = $some_hash{"frist_name"}; # autovivifies
...
[download]

I'd only use this for a few keys, in general, the other solutions offered are far superior.

In reply to Re: non-autovivifing hash by shemp
in thread non-autovivifing hash by bobdeath

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