If you happen to have a lot of patterns to match, I like the "build a sub on the fly"
approach
my @patterns = qw/ foo bar baz /;
## if you need to return the pattern itself, return '$_' instead
my $match_n_return = join( "\n",
map{ "return \$1 if \$_[0] =~ /$_/o;" } @patterns
);
my $sub = eval qq|sub { $match_n_return return undef }|;
if( $@ ) {
## some syntax error in the eval string
die $@
}
my $matched = $sub->( "string you want to match" );
The only problem here is, you don't get a fine granularity of control for each match.
But I like the fact that this can be used over and over, and that since all the regexes are
pre-compiled, you save some time for repeated use
-
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.
|