diff options
| author | Yves Orton <demerphq@gmail.com> | 2013-10-31 13:38:43 +0100 |
|---|---|---|
| committer | Yves Orton <demerphq@gmail.com> | 2013-10-31 13:43:20 +0100 |
| commit | 5e0ced9c71eb5288cc7d3c653e747b26ea6ec7b6 (patch) | |
| tree | 22ae655453b01eca179f808576015839587693e1 /pod/perllexwarn.pod | |
| parent | f789f6a4bdb5024b90845e6af62510d7f23eea5d (diff) | |
| download | perl-5e0ced9c71eb5288cc7d3c653e747b26ea6ec7b6.tar.gz | |
Add a note that users of FATAL warnings are at risk during upgrades
Apparently it isn't obvious to all of our users that use of FATAL
warnings means that peoples code may break when they upgrade due
to the introduction of new warnings. Accordingly we document that
the use of FATAL warnings is entirely at the users risk, and that
we do not and will not consider the introduction of a warning as
an incompatible change, and that in particular the use of features
which are discouraged, unspecified, or whatnot may in the future
trigger new warnings, and thus under FATAL warnings break their code.
Diffstat (limited to 'pod/perllexwarn.pod')
| -rw-r--r-- | pod/perllexwarn.pod | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/pod/perllexwarn.pod b/pod/perllexwarn.pod index d423d05894..733df81432 100644 --- a/pod/perllexwarn.pod +++ b/pod/perllexwarn.pod @@ -402,6 +402,23 @@ except for those in the "syntax" category. use warnings FATAL => 'all', NONFATAL => 'syntax'; +B<NOTE:> 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 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 NOT +consider it an incompatible change. Users of FATAL warnings should take +special caution during upgrades to check to see if their code triggers +any new warnings and should pay particular attention to the fine print of +the documentation of the features they use to ensure they do not exploit +features that are documented as risky, deprecated, or unspecified, or where +the documentation says "so don't do that", or anything with the same sense +and spirit. Use of such features in combination with FATAL warnings is +ENTIRELY AT THE USERS RISK. + =head2 Reporting Warnings from a Module X<warning, reporting> X<warning, registering> |