Because we're jerks. Patches welcome.

Seriously, it's a hard problem. Consider:

my @options = qw( foo bar ); my $string = $options[ rand @options ]; $string =~ /(foo)/; $string =~ /(bar)/; print $1;

Since there's no way of telling which option $string will contain, there's no way of telling which regex will match successfully until one actually does match successfully. (See perlvar, and note the phrase "last successful match".) The regex engine therefore has to keep track of all of the data to populate the magic variables in every regular expression.

japhy had some ideas to make this block scoped, and they may find their way into 5.10, but the problem remains hard.


In reply to Re: Why can't $` $& $' be enabled on a per-regex basis? by chromatic
in thread Why can't $` $& $' be enabled on a per-regex basis? by MrNobo1024

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.