diff options
| author | James E Keenan <jkeenan@cpan.org> | 2015-03-16 21:11:52 -0400 |
|---|---|---|
| committer | James E Keenan <jkeenan@cpan.org> | 2015-03-16 21:11:52 -0400 |
| commit | 0d314ba30623b19c36dfc97ac4b6ecb94cb406f4 (patch) | |
| tree | d26c4952946be1e1e31d63aa21f7d186907457fb /regen | |
| parent | ce3778a3796be3e4604ed9b3671ea624c5affe0b (diff) | |
| download | perl-0d314ba30623b19c36dfc97ac4b6ecb94cb406f4.tar.gz | |
perldelta entry for ce3778a3796be3e4604ed9b3671ea624c5affe0b.
Slight grammatical touch-up to cautions against FATAL warnings.
Diffstat (limited to 'regen')
| -rw-r--r-- | regen/warnings.pl | 4 |
1 files changed, 2 insertions, 2 deletions
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 |