Skip Menu |

This queue is for tickets about the ParseUtil-Domain CPAN distribution.

Report information
The Basics
Id: 92937
Status: rejected
Priority: 0/
Queue: ParseUtil-Domain

People
Owner: HEYTRAV [...] cpan.org
Requestors: CHESNOKOV [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 2.31
Fixed in: (no value)



Subject: defined(%hash) is deprecated at /opt/perlbrew/perls/perl-5.16.3/lib/site_perl/5.16.3/x86_64-linux/Unicode/CharName.pm line 80.
This error appears after running: perl Build.PL ./Build Building ParseUtil-Domain defined(%hash) is deprecated at /opt/perlbrew/perls/perl-5.16.3/lib/site_perl/5.16.3/x86_64-linux/Unicode/CharName.pm line 80. (Maybe you should just omit the defined()?) Also it's annoying that you should run `perl Build.PL` and can not run just ./Build.PL (missing a shebang line).
On Tue Feb 11 07:33:05 2014, CHESNOKOV wrote: Show quoted text
> This error appears after running: > > perl Build.PL > ./Build > > Building ParseUtil-Domain > defined(%hash) is deprecated at /opt/perlbrew/perls/perl- > 5.16.3/lib/site_perl/5.16.3/x86_64-linux/Unicode/CharName.pm line 80. > (Maybe you should just omit the defined()?) > > Also it's annoying that you should run `perl Build.PL` and can not run > just ./Build.PL (missing a shebang line).
As indicated by the message, the error appears to be in Unicode::CharName. Have you tried taking up this bug with them? I am also not the author of Module::Build. The Build.PL script is (or was at the time) generated automatically by Module::Build's bootstrapping script. It is intended to be executed by the CPAN installer. I don't plan on doing any releases in the near future, but when I do, I'll include a shebang line in the Build.PL script.
Show quoted text
> As indicated by the message, the error appears to be in Unicode::CharName. Have you tried taking up this bug with them?
You're right - sorry for disturbance, the bug is in Unicode::CharName and it appears it has been reported at 2012 (https://rt.cpan.org/Ticket/Display.html?id=74354), but still nothing has changed.
It isn't a bug of this module.