Yes, that assumption comes from using an assembled regex match. Node has been updated again to make the assumption explicit.
For kicks, let's try to handle overlapping keys using the assembled regex approach:
use Regexp::Assemble;
use Regexp::Exhaustive qw(exhaustive);
use List::Util qw(reduce);
my @keys = map { quotemeta } keys %hash;
my $key_re = Regexp::Assemble->new->add(@keys)->re;
for my $string (@strings)
{
my $match =
reduce { length($a) > length($b) ? $a : $b }
exhaustive($string => qr/\b($key_re)\b/i);
print "Found '$match' in '$string'\n"
if defined $match;
}
But then, the performance hit of using
Regexp::Exhaustive removes any justification to use the assembled regex in the first place. Ho hum.
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.