Consider also Regexp::Assemble and the following code example taken (more or less) verbatim from it: 
>perl -wMstrict -MRegexp::Assemble -le
"my $r =
   Regexp::Assemble->new->track(1)->add(qw(foo? bar{2} [Rr]at));
 for my $w (qw(this food is rather barren)) {
   if ($w =~ /$r/) {
     print qq{'$w' matched by /}, $r->source($^R), q{/};
     }
   else {
     print qq{'$w' unmatched};
     }
   }
"
'this' unmatched
'food' matched by /foo?/
'is' unmatched
'rather' matched by /[Rr]at/
'barren' matched by /bar{2}/

[download]
I haven't checked, but my guess is that this or a related method or methods from the module will give you a fairly well optimized solution.

In reply to Re: Optimize a pluggable regex matching mechanism by AnomalousMonk
in thread Optimize a pluggable regex matching mechanism by dredd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.