Glen Perkins scripsit:
> That's true, but only for the .class file's internal data encoding scheme.
> The internal encoding of a .class file doesn't matter to Java developers
> unless they want to build an app that directly parses the class file, such
> as a decompiler. Just think of it as a proprietary file format.
> Java developers who use Java's standard APIs for UTF-8 in their own (and
> others') apps get the standard UTF-8.
Except in the misnamed readUTF and writeUTF methods, which use classfile
format, and are meant for saving String objects to and from binary files,
not for general UTF-8 encoding.
-- John Cowan firstname.lastname@example.org I am a member of a civilization. --David Brin
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:53 EDT