| CC: | Joe Kline <gizmo [...] purdue.edu> |
| Subject: | Regexp-Optimizer-0.23 |
| Date: | Fri, 08 Dec 2017 10:54:24 -0500 |
| To: | bug-regexp-optimizer [...] rt.cpan.org |
| From: | Mark Senn <mark [...] ecn.purdue.edu> |
From
http://search.cpan.org/~dankogai/Regexp-Optimizer-0.23/lib/Regexp/Optimizer.pm
use Regexp::Optimizer;
my $o = Regexp::Optimizer->new->optimize(qr/foobar|fooxar|foozap/);
# $re is now qr/foo(?:[bx]ar|zap)/
Should $re be $o?
From https://perl5.git.perl.org/perl.git/blob/HEAD:/Porting/todo.pod
1006 =head2 regexp optimizer optional
1007
1008 The regexp optimizer is not optional.
It should be configurable to be optional
1009 and to allow its performance to be measured and its bugs to be easily
1010 demonstrated.
Do you keep an eye on the improvements in Perl, in case Perl with or without
/o does what Regexp-Optimizer-0.23 does?
Thanks.
Mark Senn, Systems Programmer, Engineering Computer Network, Purdue University