> I lie: the other reason qr{} currently doesn't behave like that is that
> when we interpolate a compiled regexp into a context that requires it be
> recompiled,
Interpolated qr() items shouldn't be recompiled anyway. They should
be treated as subroutine calls. Unfortunately, this requires a
In <[EMAIL PROTECTED]>, Richard Proctor writes
:
:TomCs perl storm has:
:
:> Figure out way to do
:>
:> /$e1 $e2/
:>
:> safely, where $e1 might have '(foo) \1' in it.
:> and $e2 might have '(bar) \1' in it. Those won't work.
:
:If e1 and e2 are qr// type things the answer might be to loca
This and other RFCs are available on the web at
http://dev.perl.org/rfc/
=head1 TITLE
Asignment within a regex
=head1 VERSION
Maintainer: Richard Proctor <[EMAIL PROTECTED]>
Date: 16 Aug 2000
Last Modified: 23 Sep 2000
Mailing List: [EMAIL PROTECTED]
Number: 112
Version: 3
Sta
TomCs perl storm has:
> Figure out way to do
>
> /$e1 $e2/
>
> safely, where $e1 might have '(foo) \1' in it.
> and $e2 might have '(bar) \1' in it. Those won't work.
If e1 and e2 are qr// type things the answer might be to localise
the backref numbers in each qr// expression.
If th
