The problem I have with your solution isn't so much the "cleanness", as well its inefficiency. You will be checking for direction for every comparison made by the sort - instead of checking it once.
I would do something like (untested):
my @sorted_keys =
sort {$hash{$a}{$orderby} <=> $hash{$b}{$orderby} ||
$hash{$a}{$orderby} cmp $hash{$b}{$orderby}
keys %hash;
@sorted_keys = reverse @sorted_keys if $direction eq "DESC";
foreach my $id (@sorted_keys) {
print "$id - $hash{$id}{$orderby}\n";
}
Although I vastly prefer to keep a mapping of which keys are numbers and which aren't, and don't do two tests for each non-numeric pair of keys you encounter. (Not to mention that your non-numeric entries happen to have strings that start with a number, it's going to treat them as numbers). And if I didn't I'd use a GRT to avoid the sort block. But I disgress.
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.