summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSawyer X <xsawyerx@cpan.org>2020-05-24 00:57:57 +0300
committerSawyer X <xsawyerx@cpan.org>2020-05-24 00:57:57 +0300
commitbbadd5d31911f71894e89148d3381ad18a1dc8ac (patch)
tree96c8b756729665c85c28715db0f89b680fd750e8
parent4db50d5b5d47352292dad224cee41ca57ff05a38 (diff)
downloadperl-bbadd5d31911f71894e89148d3381ad18a1dc8ac.tar.gz
Correct text on my() in false conditional
-rw-r--r--pod/perldeprecation.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/pod/perldeprecation.pod b/pod/perldeprecation.pod
index 0f46480e12..4faa9a8527 100644
--- a/pod/perldeprecation.pod
+++ b/pod/perldeprecation.pod
@@ -242,7 +242,7 @@ See L<perlfunc/dump>.
There has been a long-standing bug in Perl that causes a lexical variable
not to be cleared at scope exit when its declaration includes a false
conditional. Some people have exploited this bug to achieve a kind of
-static variable. Since we intend to fix this bug, we don't want people
+static variable. To allow us to fix this bug, people should not be
relying on this behavior.
Instead, it's recommended one uses C<state> variables to achieve the
@@ -256,7 +256,7 @@ same effect:
C<state> variables were introduced in Perl 5.10.
Alternatively, you can achieve a similar static effect by
-declaring the variable in a separate block outside the function, eg
+declaring the variable in a separate block outside the function, e.g.,
sub f { my $x if 0; return $x++ }
@@ -265,7 +265,7 @@ becomes
{ my $x; sub f { return $x++ } }
The use of C<my()> in a false conditional has been deprecated in
-Perl 5.10, and it will become a fatal error in Perl 5.30.
+Perl 5.10, and became a fatal error in Perl 5.30.
=head3 Reading/writing bytes from/to :utf8 handles.