Another solution is using (abusing?) list auto-stringification, or multidimensional emulation. (How long should the term be for something so simple?) Instead of all those cool hash-reference trees, you could use a flat hash with namespaced keys, just like your file. If you feed perl a list for a hash key, it will apply a
join('', ...) to it. (I believe there is a
perlvar to change the separator, though. <looks> Oh, It's
$;) After you build the hash this way, walking your tree is is as simple as
sort keys.
$; = ':';
my %Hash;
while (<>) {
chomp $_;
my ($key, $val) = split(/=/);
if ($key =~ /:/) {
my @keyparts = split(/$;/, $key);
$Hash{ join("$;", @keyparts) } = $val;
# I'm not sure how to get perl to not scalar-ize it in this ca
+se
# But it's probably better to reduce cargo-cultism ;)
} else {
$Hash{$key} = $val;
}
}
foreach (sort keys %Hash) {
print "$_ \t=> " . $Hash{$_} . "\n";
}
print $Hash{'a1','b1','c1'} . "\n"
mhoward - at - hattmoward.org
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.