summaryrefslogtreecommitdiff
path: root/pod/perlre.pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2000-03-03 02:26:53 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2000-03-03 02:26:53 +0000
commit09cc1b93b147afa99fbf83f5d0366d3467ba6fba (patch)
tree0d9a49e04abe0701438fe63c6d0988bdd5dfb7df /pod/perlre.pod
parent2a3be124a967e8b8c2b63eba4b01fc25cc9ee755 (diff)
parent14455d6cc193f1e4316f87b9dbe258db24ceb714 (diff)
downloadperl-09cc1b93b147afa99fbf83f5d0366d3467ba6fba.tar.gz
Integrate with Sarathy.
p4raw-id: //depot/cfgperl@5469
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 6dd98ae3bf..64f7f1cdcb 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.