summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorDominic Dunlop <domo@computer.org>2006-04-02 23:13:59 +0200
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2006-04-03 08:30:27 +0000
commit8988a1bb3fb8fac6b97385be1a1d8b9945b1e29e (patch)
tree010ab36672089d9fed4afdfdf009b2242d93b7d2 /pod
parentc99ffe5e27f50044d8e283a2c6c45b050a7bcce0 (diff)
downloadperl-8988a1bb3fb8fac6b97385be1a1d8b9945b1e29e.tar.gz
Document that the regexp engine is not currently reentrant
Subject: Re: [perl #33936] segment fault when using split() in regexp with (??{...}) Message-Id: <AD104FE7-2BD6-49B6-A845-46458179A4B1@computer.org> p4raw-id: //depot/perl@27697
Diffstat (limited to 'pod')
-rw-r--r--pod/perlre.pod8
1 files changed, 8 insertions, 0 deletions
diff --git a/pod/perlre.pod b/pod/perlre.pod
index 32a7e6fcf7..04c92d5ea2 100644
--- a/pod/perlre.pod
+++ b/pod/perlre.pod
@@ -694,6 +694,10 @@ so you should only do so if you are also using taint checking.
Better yet, use the carefully constrained evaluation within a Safe
compartment. See L<perlsec> for details about both these mechanisms.
+Because perl's regex engine is not currently re-entrant, interpolated
+code may not invoke the regex engine either directly with C<m//> or C<s///>),
+or indirectly with functions such as C<split>.
+
=item C<(??{ code })>
X<(??{})>
X<regex, postponed> X<regexp, postponed> X<regular expression, postponed>
@@ -724,6 +728,10 @@ The following pattern matches a parenthesized group:
\)
}x;
+Because perl's regex engine is not currently re-entrant, delayed
+code may not invoke the regex engine either directly with C<m//> or C<s///>),
+or indirectly with functions such as C<split>.
+
=item C<< (?>pattern) >>
X<backtrack> X<backtracking>