Christopher Brien wrote:
> Isn't Java supposed to be capable of recognising all unicode and ascii 
> text formats? If Jikes can't handle that, then it's a problem with 
> Jikes. It would probably be best informing the people working on it 
> about this problem, because it's likely to recur. Rewriting the entire 
> source in a single text format is not a reasonable option.

And meanwhile, you have to use a proprietary program to compile the 
code.  Right?

Anyway, there's maybe less than 10 non-ASCII character in the whole 
Classpath CVS (should be verified).  Why not encode these using "unicode 
escapes", e.g.: \u1023 ?  The Java designers did this exactly to 
minimize the problems of compiling code under various platforms.

Etienne
-- 
Etienne M. Gagnon                               [EMAIL PROTECTED]
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/


_______________________________________________
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath

Reply via email to