I'm checking this in.
This sets Classpath's file encoding to "UTF-8". It updates the
documentation and the Makefile, except for the kjc case, as according
to the web pages I found, kjc doesn't support an encoding option (and
I don't have it installed). I tested only tested this with gcj.
Tom
I
Tom Tromey wrote:
> I'm checking this in.
>
> This sets Classpath's file encoding to "UTF-8".
The version of Jikes I use (1.22 on Windows) doesn't support the
-encoding option. Are there any pressing reasons why we can't simply
stick to ASCII?
Regards,
Jeroen
__
> "Jeroen" == Jeroen Frijters <[EMAIL PROTECTED]> writes:
Jeroen> The version of Jikes I use (1.22 on Windows) doesn't support the
Jeroen> -encoding option. Are there any pressing reasons why we can't simply
Jeroen> stick to ASCII?
Sorry, I didn't realize that the windows jikes didn't support
Tom Tromey wrote:
> > "Jeroen" == Jeroen Frijters <[EMAIL PROTECTED]> writes:
>
> Jeroen> The version of Jikes I use (1.22 on Windows) doesn't
> support the
> Jeroen> -encoding option. Are there any pressing reasons why
> we can't simply
> Jeroen> stick to ASCII?
>
> Sorry, I didn't realize
> "Jeroen" == Jeroen Frijters <[EMAIL PROTECTED]> writes:
Jeroen> I personally don't use the Classpath build infrastructure, so I don't
Jeroen> mind the option being in there (although it would be nice not to set it
Jeroen> when running on Windows), but since I have no way of specifying UTF-8
Tom Tromey wrote:
> I think the problem is that without '-encoding' there is no way to
> enforce this constraint, as compilers tend to use the locale's
> encoding.
I understand, but what I meant was that we can try to enforce ASCII
encoding on the platforms that support it and other platforms it w
