Simply for the laziness of using
List::Util. But if you're gonna optimize it, why check both conditions? An element can't be the maximum and the minimum at the same time. You're also pulling the list of all keys twice.
my ($min, $max) = (scalar each %h) x 2;
($min, $max) = (
$h{$_} < $h{$min} ? ($_, $max) :
$h{$_} > $h{$max} ? ($min, $_) :
($min, $max)
) for keys %h;
You could even go all out on
each to remove the last bit of redundant work, and to reduce memory footprint.
my $min = each %h;
my $max = each %h;
if(defined $max) {
local $_;
($min, $max) = (
$h{$_} < $h{$min} ? ($_, $max) :
$h{$_} > $h{$max} ? ($min, $_) :
($min, $max)
) while defined($_ = each %h);
}
else {
$max = $min;
}
That's all cool if your hash is really huge. If it's just a couple pairs, I'll prefer the lazy route any day.
Makeshifts last the longest.
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.