diff options
| author | David Mitchell <davem@iabyn.com> | 2012-06-13 17:29:27 +0100 |
|---|---|---|
| committer | David Mitchell <davem@iabyn.com> | 2012-06-14 09:02:01 +0100 |
| commit | e128ab2c0803fa45e7f26de2941696d173a9a293 (patch) | |
| tree | 90ea68d121f7a4a49e0421667b1b2118386db114 /ext | |
| parent | e07bb5160f6400c20751be8384bb3458270effde (diff) | |
| download | perl-e128ab2c0803fa45e7f26de2941696d173a9a293.tar.gz | |
update docs for (?{}) jumbo fix
Update the docs and add perldelta entries summarising the changes and
fixes related to (?{}) and (??{}) accumulated over the 120 or so commits
in this branch.
Diffstat (limited to 'ext')
| -rw-r--r-- | ext/re/re.pm | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/ext/re/re.pm b/ext/re/re.pm index d72b6f4962..75452b8a45 100644 --- a/ext/re/re.pm +++ b/ext/re/re.pm @@ -284,8 +284,9 @@ other transformations. When C<use re 'eval'> is in effect, a regexp is allowed to contain C<(?{ ... })> zero-width assertions and C<(??{ ... })> postponed -subexpressions, even if the regular expression contains -variable interpolation. That is normally disallowed, since it is a +subexpressions that are derived from variable interpolation, rather than +appearing literally within the regexp. That is normally disallowed, since +it is a potential security risk. Note that this pragma is ignored when the regular expression is obtained from tainted data, i.e. evaluation is always disallowed with tainted regular expressions. See L<perlre/(?{ code })> |