From e9158b84fe735f37141c35ffabc02ac81dd2ea4b Mon Sep 17 00:00:00 2001 From: Father Chrysostomos Date: Thu, 31 Oct 2013 05:46:39 -0700 Subject: [PATCH] perllexwarn: typo, pod syntax --- pod/perllexwarn.pod | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/pod/perllexwarn.pod b/pod/perllexwarn.pod index 733df81..d632920 100644 --- a/pod/perllexwarn.pod +++ b/pod/perllexwarn.pod @@ -402,7 +402,8 @@ except for those in the "syntax" category. use warnings FATAL => 'all', NONFATAL => 'syntax'; -B Users of FATAL warnings, especially those using C 'all'> +B 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 @@ -417,7 +418,7 @@ 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. +ENTIRELY AT THE USER'S RISK. =head2 Reporting Warnings from a Module X X -- 2.7.4