You can use the experimental (?{...}) code groups in the generated regex:

use strict; use warnings; use 5.010; use re 'eval'; my %h = ( '^foo' => sub { say 'foo' }, '^bar' => sub { say 'bar' }, ); my $what; my $re = join '|', map { "$_(?{\$what = '$_'})" } keys %h; if ('foo' =~ m/$re/o) { $h{$what}->(); }

But be sure to read the warnings in perlre.

Note that this requires the keys not to contain ' or \, but you could easily give them identifier labels instead, or properly escape $_ before interpolation.

(5.010 only required for say).

Perl 6 - links to (nearly) everything that is Perl 6.

In reply to Re: Optimize a pluggable regex matching mechanism by moritz
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.