On Mon, 3 Feb 1997 unicode@Unicode.ORG wrote:
> The GNU C compiler, gcc, did not issue any error messages, but the compiled
> object program did not print anything (I may have invoked this compiler with
> inappropriate arguments, but I do not have the time to explore gcc's idio-
> syncracies).
It appears as though gcc's \x handling in wide strings is broken,
at least in 2.7.2.1. However \x does work in a character
constant, eg L'\x4e00', and if the L is omitted from the string
constant, the compiler does issue a warning that the escape
sequence is out of range.
Looks like they intended for it to work, but something got
botched in the implementation. :(
-john
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:33 EDT