* Pali Rohár <pali(_dot_)rohar(_at_)gmail(_dot_)com> [2016-05-12 20:23]:
If both functions should do same thing, why we have duplicity?
Encode.pm is big and fairly slow, because it handles a zillion encodings
and has lots of options for handling invalid input data. Perl needs only
UTF-8 transcoding and needs it fast, so it has code for just that. Since
that code is there anyway, it can just as well be exposed to Perl space.
And which one is preferred to use?
Well, either you need Encode.pm or you don’t. The built-ins are faster
and always loaded, but they only do UTF-8 and if you have invalid data
then all you get is a false return value and no other help. If you need
anything else you pay the memory and take the speed hit of Encode.pm.
(If you are working on a large application, chances are high that you
have Encode.pm loaded anyway.)
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
