summaryrefslogtreecommitdiff
path: root/pod/perlre.pod
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2000-03-03 02:19:50 +0000
committerGurusamy Sarathy <gsar@cpan.org>2000-03-03 02:19:50 +0000
commit14455d6cc193f1e4316f87b9dbe258db24ceb714 (patch)
tree0722cfd9590d6e717d6a7f06bbb534593146dee6 /pod/perlre.pod
parent36f31b5005f0d5567cbdeeea5b6180abf2936b23 (diff)
downloadperl-14455d6cc193f1e4316f87b9dbe258db24ceb714.tar.gz
/(?p{})/ changed to /(??{})/, per Larry's suggestion (from
Simon Cozens <simon@othersideofthe.earth.li>) p4raw-id: //depot/perl@5467
Diffstat (limited to 'pod/perlre.pod')
-rw-r--r--pod/perlre.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/pod/perlre.pod b/pod/perlre.pod
index d2f64d2eb6..52eac04a34 100644
--- a/pod/perlre.pod
+++ b/pod/perlre.pod
@@ -570,7 +570,7 @@ so you should only do so if you are also using taint checking.
Better yet, use the carefully constrained evaluation within a Safe
module. See L<perlsec> for details about both these mechanisms.
-=item C<(?p{ code })>
+=item C<(??{ code })>
B<WARNING>: This extended regular expression feature is considered
highly experimental, and may be changed or deleted without notice.
@@ -592,7 +592,7 @@ The following pattern matches a parenthesized group:
(?:
(?> [^()]+ ) # Non-parens without backtracking
|
- (?p{ $re }) # Group with matching parens
+ (??{ $re }) # Group with matching parens
)*
\)
}x;
@@ -1175,7 +1175,7 @@ else in the whole regular expression.)
For this grouping operator there is no need to describe the ordering, since
only whether or not C<S> can match is important.
-=item C<(?p{ EXPR })>
+=item C<(??{ EXPR })>
The ordering is the same as for the regular expression which is
the result of EXPR.