Although by comparison lookahead and behind might get better performance because of less passes per line of text,
sauoq's idea of simply removing the exceptions, which became just a few lines inserted into the orginal code still managed to performed very well indeed (still only a second or two through the whole tree). Notice that $_ is getting all the exceptions removed from it cumulatively, i.e. including for other search strings, but that doesn't do any damage given that the parameters of the problem already preclude one search string being a substring of another by reductio ad absurdum.
sub SmartSearch {
my $srch = shift;
my $eref = $_{ EXC }{ $srch };
for my $exc ( keys %$eref ) {
s/$exc//g;
}
return /$srch/;
}
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.