In perl.git, the branch blead has been updated

<http://perl5.git.perl.org/perl.git/commitdiff/6a807e2131bdd208d856c632a661bea960643322?hp=deaf6ad33bc791827dc72b549e911a4a2d1a0886>

- Log -----------------------------------------------------------------
commit 6a807e2131bdd208d856c632a661bea960643322
Author: Karl Williamson <k...@cpan.org>
Date:   Tue Apr 22 18:31:11 2014 -0600

    perldiag: Clarify non-char warning
    
    What to do in this situation is currently subject to ticket
    [perl #121226],  This more clearly documents what happens now.
-----------------------------------------------------------------------

Summary of changes:
 pod/perldiag.pod |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index 00700c5..bca95e2 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -5742,9 +5742,15 @@ with the characters in the Lao and Thai scripts.
 (S nonchar) Certain codepoints, such as U+FFFE and U+FFFF, are
 defined by the Unicode standard to be non-characters.  Those are
 legal codepoints, but are reserved for internal use; so, applications
-shouldn't attempt to exchange them.  If you know what you are doing
+shouldn't attempt to exchange them.  An application may not be
+expecting any of these characters at all, and receiving them
+may lead to bugs.  If you know what you are doing
 you can turn off this warning by C<no warnings 'nonchar';>.
 
+This is not really a "serious" error, but it is supposed to be raised
+by default even if warnings are not enabled, and currently the only
+way to do that in Perl is to mark it as serious.
+
 =item Unicode surrogate U+%X is illegal in UTF-8
 
 (S surrogate) You had a UTF-16 surrogate in a context where they are

--
Perl5 Master Repository

Reply via email to