Using the following technique, you can encapsulate your regexes in anonymous subroutines, that can easily be called with the string to change as first argument. They return the changed string. Like this:

#list of regex-strings
my @regex =
(
    's/(a+)/\U$1/g',
    's/([bz]+)/XX/g',
);

#is now a list of subroutines
@regex = map { eval "\$sub = sub { \$_=\$_[0]; $_; \$_ }" } @regex;
[download]

This list can easily be used like this:

my @text = 
(
    "aaaabbzz",
    "bbbyyy",
);

for my $t ( @text )
{
    print "org $t\n";
    for my $re ( @regex )
    {
        $t = &$re($t);
    }
    print "new  $t\n";
}
[download]

Encapsulating the regexes in subroutines should be faster than recompiling the same regex again and again. Note, that I did no benchmarks.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.