* Father Chrysostomos <sprout@cpan.org> [2016-05-21 22:40]: > 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 I think so. I remember thinking it was a great idea when I first heard about it, but I can no longer figure out why, and to my current self it seems obviously misguided in premise and purpose. > probably reinforced by encoding.pm's model, which never really made > sense to me. Personally I doubt that encoding.pm in particular was an influence in its design. Not that it matters. > 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. The question to my mind is whether there are users who depend on it in their production environments. If there is a non-zero amount of such users then it must be phased out gradually, however misguided its use. It does not seem likely to me that a significant such group exists, but that may just as well be a failure of imagination on my part. Do we have any indicators about that? Any anecdotal evidence? If it is used as a development aid only, then I think it would be fine to just make it a no-op that warns on import(). Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>Thread Previous | Thread Next