Is it finally time to remove the sun.io converters?
Ulf.Zibis at gmx.de
Tue Jun 14 03:34:23 PDT 2011
Am 14.06.2011 10:25, schrieb Alan Bateman:
> Ulf Zibis wrote:
>> As replacement for the 323 classes in original sun.io you could use my wrapper classes:
>> There remain only 8 classes.
> I think this should be backup, as in a plan B. The JDK documentation has always warned developers
> not to use sun.* APIs. javac has even emitted warnings since the symbol file mechanism was added
> (jdk6?). In the case of sun.io then there's been a better solution (java.nio.charsets) since 1.4
> and so folks have had nearly 9 years to move. They will have at least 10 or more years by the time
> that jdk8 ships. With modules coming in jdk8 then it seems a good opportunity to move on this.
I mentioned this, because (1) in the meantime you could save ~300 classes, (2) must no more maintain
sun.io if there are new encodings and (3) I did so much effort in those wrappers, so I would like to
see them living. :-X
But anyway, I would like to see sun.io package removed.
Don't forget weather sun.io package is removed or replaced by my wrapper:
Almost all *Charset classes in sun.nio package* could be made *package private*, so no one can
access them externally.
More information about the core-libs-dev