comment on

which gives you the efficiency of performing a single match,

A single match is not always more efficient. A bunch of simple matches can be more efficient than a single, more complicated, match. And that's because of the Perl optimizer. Here's an example:

#!/usr/bin/perl

use strict;
use warnings;

use Regexp::Assemble;
use Perl6::Slurp;

use Benchmark qw /cmpthese/;
use Test::More tests => 1;

our @data = slurp '/usr/share/dict/words';

our(@a, @b);

cmpthese(-10, {
    regex => '@a = grep {/qu/ || /x/} @data',
    ra    => 'my $re = Regexp::Assemble->new->add("qu")->add("x")->re;
              @b = grep {/$re/} @data',
});

is_deeply(\@a, \@b);

__END__
1..1
        Rate    ra regex
ra    4.71/s    --  -65%
regex 13.5/s  186%    --
ok 1
[download]

In reply to Re^2: Regex and question of design by Anonymous Monk
in thread Regex and question of design by amaguk

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.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks