jcwren, what
merlyn wanted was to have you build a
hash lookup for the original command, and get the actual
code-ref from a double lookup.
Building an initial hash and working from that is clearly
a nicer algorithm than grepping every time. However
Text::Abbrev will not allow him to disambiguate the case
where the match is ambiguous from simply not found. Now
is that detail important? My take is that for anything
meant for interactive use it is a critical distinction to
make. It really matters to the UI.
OTOH the algorithmic improvement is not dependent upon the
library module. Untested:
sub build_lookup {
my %lookup;
foreach my $str (@_) {
foreach my $len (1..length($str)) {
my $portion = substr($str, 0, $len);
push @{$lookup{$portion}}, $str;
}
}
return %lookup;
}
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.