Further, every time you use capturing brackets, all the captured chunks are also copied--again.
Not exactly ;)
Q:\>perl -le "($x = 'foo') =~ /.(.)/g; print $1; $x = 'bar'; print $1" o a This is perl, v5.8.2 built for MSWin32-x86-multi-thread
Of course, the /g modifier there is a bug in the code, but it still shows that not in every case, a capturing match copies the buffer.
Thanks to dave_the_m and demerphq's recent work, the Perl5.10 regex engine is improving even more beyond the C recursion elimination. It has named captures that bring it up to par and beyond what the other named captures provide, and it has quite the speedup against Unicode strings as far as I understand the changes. There are some deeper problems with how closures-in-regular expressions are handled vs. interpolation (in (?{..}) blocks).
This post is mostly about adding some perspective to the changes that happen to the regex engine ;)
In reply to Re: Things you should need to know before using Perl regexes. (Humour, with a serious point)
by Corion
in thread Things you should need to know before using Perl regexes. (Humour, with a serious point)
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |