develooper Front page | perl.perl5.porters | Postings from May 2016

Re: Whither encoding::warnings?

Thread Previous | Thread Next
From:
George Greer
Date:
May 23, 2016 19:52
Subject:
Re: Whither encoding::warnings?
Message ID:
alpine.LFD.2.20.1605231547550.20040@drei.m-l.org
On Sat, 21 May 2016, Father Chrysostomos wrote:

> Whither encoding::warnings?
>
> I tried removing ${^ENCODING}, but tests for encoding::warnings fail.
> See the sprout/encoding branch.
>
> Before working on this any further, I need to ask what the plan is for
> encoding::warnings.
>
> Reading the POD of the module, I don't really understand its purpose.
> It seems to be based on a faulty understanding of Perl's Unicode
> model, probably reinforced by encoding.pm's model, which never really
> made sense to me.
>
> Do we need to put encoding::warnings through a deprecation cycle?  Or
> can we simply disable it (or make it a no-op) for Perl 5.26 onwards?
>
> Much work has been put into making sure that accidental upgrading of
> "\xff" to "\N{0+FF}" will have no ill effects; hence, warning about
> that seems unnecessary.


We rely on it at $WORK because we can't assume the source text is Latin-1 
and both sides should have already been upgraded before doing operations.


-- 
George Greer

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About