From: Father Chrysostomos <sprout@cpan.org>
Date: Sun, 13 Feb 2011 20:36:39 +0000 (-0800)
Subject: Improve perldiag/Eval-group not allowed at runtime
X-Git-Tag: v5.13.10~275
X-Git-Url: https://perl5.git.perl.org/perl5.git/commitdiff_plain/f11307f50aedbc1043359a6926fe4060854fc893?hp=f94762723eddc4a0de865db28c07e020aecf8d06

Improve perldiag/Eval-group not allowed at runtime

• Mention use re 'eval' within the description
• Improve text flow
---

diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index 3338d71..82e6889 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -1698,10 +1698,11 @@ is unsafe.  See L<perlre/(?{ code })>, and L<perlsec>.
 
 (F) Perl tried to compile a regular expression containing the
 C<(?{ ... })> zero-width assertion at run time, as it would when the
-pattern contains interpolated values.  Since that is a security risk, it
-is not allowed.  If you insist, you may still do this by explicitly
-building the pattern from an interpolated string at run time and using
-that in an eval().  See L<perlre/(?{ code })>.
+pattern contains interpolated values.  Since that is a security risk,
+it is not allowed.  If you insist, you may still do this by using the
+C<re 'eval'> pragma or by explicitly building the pattern from an
+interpolated string at run time and using that in an eval().  See
+L<perlre/(?{ code })>.
 
 =item %s: Eval-group not allowed, use re 'eval'