Bug 834867 - [PATCH] "defined(%hash) is deprecated" warning in Unicode::CharName
Summary: [PATCH] "defined(%hash) is deprecated" warning in Unicode::CharName
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Unicode-String
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Emmanuel Seyman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-24 12:29 UTC by Paul Howarth
Modified: 2012-06-24 15:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-24 15:37:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Debian patch fixing the warning (506 bytes, application/x-download)
2012-06-24 12:29 UTC, Paul Howarth
no flags Details


Links
System ID Private Priority Status Summary Last Updated
CPAN 74354 0 None None None 2012-06-24 15:00:50 UTC
Debian BTS 657144 0 None None None 2012-06-24 12:29:15 UTC

Description Paul Howarth 2012-06-24 12:29:14 UTC
Created attachment 593995 [details]
Debian patch fixing the warning

On newer perls (all current Fedora releases including 15 are affected), use of this module results in a deprecation warning. It's visible in the test suite:

$ make test
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/byteswap.t ... ok
defined(%hash) is deprecated at /builddir/build/BUILD/Unicode-String-2.09/blib/lib/Unicode/CharName.pm line 80.
        (Maybe you should just omit the defined()?)
t/charname.t ... ok
t/encoding.t ... ok
t/op.t ......... ok
t/ord.t ........ ok
t/stringify.t .. ok
All tests successful.
Files=6, Tests=112,  0 wallclock secs ( 0.03 usr  0.01 sys +  0.10 cusr  0.02 csys =  0.16 CPU)
Result: PASS

Attached patch is from the debian bug for the same issue.

Comment 1 Emmanuel Seyman 2012-06-24 15:00:50 UTC
Note that this has been upstreamed as #74354 on CPAN's RT.

Comment 2 Emmanuel Seyman 2012-06-24 15:37:15 UTC
Fixed. Thanks for reporting the issue, Paul.


Note You need to log in before you can comment on or make changes to this bug.