I like the idea a lot. Performance, although not to be neglected when thinking about how a feature will affect the average case, is not so much motivation to me as the fact that this provides a clean way to do it Once And Only Once. Right now, there is no way to achieve that for
exists tests. For multilevel lookups you can roll up the lookup for most of the path which gets close, but no cigar:
exists $_->{$client} and return $_->{$client}
for $export_def->{'..client_default_version'};
But there's just no way around the duplicate mention of
$client. And just as I was typing this code, I forgot the sigil in the second lookup and only by chance caught it a few seconds before submitting, which demonstrates why Once And Only Once is a good idea. Had I made this mistake in actual code, it would have broken silently and possibly left me to scratch my head for a long time.
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.