In terms of expressing intent, at least in my biased opinion, the original code fragment wins, and the attempts at "making it better" are increasingly obfuscating. Unless performance is a serious issue, clarity of expression should be the goal.
Consider picking up the code blind. Which is easier to understand?
foreach $oldkey (keys %fdat) {
if ( ($newkey = $oldkey) =~ s/^redirect_//) {
$fdat{$newkey} = $fdat{$oldkey};
}
}
or
$fdat{$_} = $fdat{"redirect_$_"}
for map { /^redirect_(.*)$/ ? $1 : () } keys %fdat;
I consider myself a pretty fair Perl coder, but I have to admit that it took me an order of magnitude longer to grasp the intent of the second example than it did the first. When I catch folks in my team writing code like the second example, we have a talk. The talk includes asking them to consider the plight of the poor soul who has to pick up the code next.
Clarity, please.
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.