summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJames E Keenan <jkeenan@cpan.org>2015-03-16 21:11:52 -0400
committerJames E Keenan <jkeenan@cpan.org>2015-03-16 21:11:52 -0400
commit0d314ba30623b19c36dfc97ac4b6ecb94cb406f4 (patch)
treed26c4952946be1e1e31d63aa21f7d186907457fb
parentce3778a3796be3e4604ed9b3671ea624c5affe0b (diff)
downloadperl-0d314ba30623b19c36dfc97ac4b6ecb94cb406f4.tar.gz
perldelta entry for ce3778a3796be3e4604ed9b3671ea624c5affe0b.
Slight grammatical touch-up to cautions against FATAL warnings.
-rw-r--r--lib/warnings.pm4
-rw-r--r--pod/perldelta.pod8
-rw-r--r--regen/warnings.pl4
3 files changed, 12 insertions, 4 deletions
diff --git a/lib/warnings.pm b/lib/warnings.pm
index 86cf0272ac..765f60d7dc 100644
--- a/lib/warnings.pm
+++ b/lib/warnings.pm
@@ -895,8 +895,8 @@ believes that FATAL warnings should not be used.
Moreover, users of FATAL warnings, especially those using
C<< FATAL => 'all' >> should be fully aware that they are risking future
portability of their programs by doing so. Perl makes absolutely no
-commitments to not introduce new warnings, or warnings categories in the
-future, and indeed we explicitly reserve the right to do so. Code that may
+commitments to not introduce new warnings or warnings categories in the
+future; indeed, we explicitly reserve the right to do so. Code that may
not warn now may warn in a future release of Perl if the Perl5 development
team deems it in the best interests of the community to do so. Should code
using FATAL warnings break due to the introduction of a new warning we will
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 3c346357e1..cf96a9b118 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -49,6 +49,10 @@ XXX For a release on a stable branch, this section aspires to be:
XXX Any deprecated features, syntax, modules etc. should be listed here.
+=head2 FATAL warnings are now discouraged
+
+Cautions against use of FATAL warnings have been strengthened.
+
=head2 Module removals
XXX Remove this section if inapplicable.
@@ -232,6 +236,10 @@ L<utf8> has been upgraded from version 1.14 to 1.15.
L<XS::APItest> has been upgraded from version 0.70 to 0.71.
+=item *
+
+L<warnings> has been upgraded from version 1.31 to 1.32.
+
=back
=head2 Removed Modules and Pragmata
diff --git a/regen/warnings.pl b/regen/warnings.pl
index 8f1e0ff71c..db9cc2532a 100644
--- a/regen/warnings.pl
+++ b/regen/warnings.pl
@@ -1011,8 +1011,8 @@ believes that FATAL warnings should not be used.
Moreover, users of FATAL warnings, especially those using
C<< FATAL => 'all' >> should be fully aware that they are risking future
portability of their programs by doing so. Perl makes absolutely no
-commitments to not introduce new warnings, or warnings categories in the
-future, and indeed we explicitly reserve the right to do so. Code that may
+commitments to not introduce new warnings or warnings categories in the
+future; indeed, we explicitly reserve the right to do so. Code that may
not warn now may warn in a future release of Perl if the Perl5 development
team deems it in the best interests of the community to do so. Should code
using FATAL warnings break due to the introduction of a new warning we will