This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: thoughts on martin's proposed patch for GCC and UTF-8
- To: Paul Eggert <eggert at twinsun dot com>
- Subject: Re: thoughts on martin's proposed patch for GCC and UTF-8
- From: Per Bothner <bothner at cygnus dot com>
- Date: Mon, 21 Dec 1998 20:30:26 -0800
- cc: gcc2 at gnu dot org, egcs at cygnus dot com
> libc's identifiers use only the "C" subset of ASCII, and therefore
> libc will link to an application written in any locale, even if we use
> the native multibyte encoding for identifiers.
It was an example. In practice, libraries meant for other-than-internal
use will probably stick to the C subset - but I don't want to
depend on that.
> I don't see how this follows. The compiler could use autodetection to
> discover the input character set, and then translate the identifiers'
> characters to UTF-8 when outputting assembly language.
We've already established that the compiler cannot use autodetection
to discover the input character set except in very specific environments.
I guess I was responding to the idea of passing uninterpreted
bytes through, and pointing that that is a bad idea for at least
external identifiers and for Java.
--Per Bothner
Cygnus Solutions bothner@cygnus.com http://www.cygnus.com/~bothner