Change charnames.t to cope with new Perl core charnames.pm #4

Merged
merged 1 commit into from Oct 23, 2012

Conversation

Projects
None yet
2 participants

Version 1.33 of charnames.pm is changing in conjunction with core Perl 5
to make \N{ANY UNKNOWN CHARACTER} fatal, instead of merely being a
warning. This will now conform to the behavior that Unicode recommends.

This commit causes charnames.t to expect a warning from versions of
charnames.pm earlier than 1.33, and a fatal error beginning with 1.33.

Feel free to alter this in any way you like. I intend to make the charnames.pm changes to blead soon, unless you object, and they should be in the next development release 5.17.6.

Karl Williamson charnames.t: Fix to work with new charnames.pm
Version 1.33 of charnames.pm is changing in conjunction with core Perl
to make \N{ANY UNKNOWN CHARACTER} fatal, instead of merely being a
warning.  This will now conform to the behavior that Unicode recommends.

This commit causes charnames.t to expect a warning from versions of
charnames.pm earlier than 1.33, and a fatal error beginning with 1.33.
eeb170d

@miyagawa miyagawa added a commit that referenced this pull request Oct 23, 2012

@miyagawa miyagawa Merge pull request #4 from khwilliamson/master
Change charnames.t to cope with new Perl core charnames.pm
e64f038

@miyagawa miyagawa merged commit e64f038 into miyagawa:master Oct 23, 2012

@miyagawa miyagawa added a commit that referenced this pull request Oct 23, 2012

@miyagawa miyagawa Checking in changes prior to tagging of version 0.30.
Changelog diff is:

diff --git a/Changes b/Changes
index 4281b65..d5c0efe 100644
--- a/Changes
+++ b/Changes
@@ -1,5 +1,8 @@
 Revision history for Perl extension Encode::JP::Mobile

+0.30  Mon Oct 22 18:16:57 PDT 2012
+        - Support new charnames.pm in tests where unknown character name throws fatal errors (Karl Williamson) #4
+
 0.29  Tue Oct 16 17:59:29 PDT 2012
         - Fixses issues with re.pm between on perl 5.14 and 5.16 (tokuhirom)
2636511
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment