Solaris -vs- iconv

Mon Apr 2 18:55:00 GMT 2001

Tom Tromey wrote:
> The individual decisions we've made are all reasonable (IMHO) but add
> up to an unreasonable whole :-(
>> * We want to use the user's locale by default.
> This is what javac claims to do, so following it is almost a
> requirement.
>> * We want to use the system iconv if it is available
> One reason for this is simply that we don't already have an iconv()
> replacement in the tree, and we've already made the gcc tree much
> larger with our required libraries. Adding an iconv replacement
> (and there is at least one good free one) on top of this seems like
> a pain. We could check for and use it if it is available, but this
> won't help typical Solaris users.

I imagine that there are other platforms besides Solaris that don't have
a good-enough iconv() for our purposes, right? So having the option of
using an iconv implementation from the tree seems like ultimatley the
best solution. Especially if it can be shared between libgcj and gcj.
So the JDK, and by extension, javac, have their own character converters,
probibly written in Java, and thus don't need iconv? What does jikes do?
regards
 [ bryce ]