> Oh, sure, that works. But that isn't very much different from using:

> /(foo\d+)|(bar\S+?)/

> and checking which of $1 or $2 is defined.

For my approach it's much easier to construct more complicated regexes like

/pre(§FOO§|§BAR§)post/

In this rather simple example FOO and BAR are $2 and $3!

I think the idea of the OP is to use regexes as rules and to efficiently check which rules apply.

My initial approach would be to further investigate the matched string for each rule.

But the named match approach has many benefitsecause I will in any way need to have a hash holding the rules.

> and consult $REGMARK afterwards.

experimental feature! :(

Cheers Rolf

In reply to Re^7: Regex: return the pattern instead of the actual match by LanX
in thread Regex: return the pattern instead of the actual match by Deus Ex

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.