Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • In Java, a java.lang.String and a byte[] have nothing in common, and there are no (non-deprecated) ways of converting between them without specifying an encoding. It's one of the very few features I like about Java…
    • There are (at least) two things wrong with Java's encoding support:
      1. No way to avoid UnsupportedEncodingException, even for UTF-8, which is guaranteed to be present.
      2. The concept of a "system default encoding" is flawed and leads to bugs in portability. You should be forced to always specify an encoding.
        1. true
        2. I thought all methods that converted without specifying an enconding were deprecated… anyway, yes, implicit encondings are a very bad idea

        and while we're at it,

        3. internal enconding is utf-16, and it's visible at the language level, so that the "length" method gives you completely useless information

        • Very true about the 16 bit character. Thankfully, it's less of a problem for me right now.