Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!zaphod.mps.ohio-state.edu!rpi!uupsi!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: wchar_t values
Message-ID: <15829@smoke.brl.mil>
Date: 15 Apr 91 21:58:22 GMT
References: <keld.670719584@dkuugin> <HARKCOM.91Apr5091146@spinach.pa.yokogawa.co.jp> <1107@sranha.sra.co.jp>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 11

In article <1107@sranha.sra.co.jp> erik@srava.sra.co.jp (Erik M. van der Poel) writes:
>I.e. 10646 'c' does not have the same numeric value as ASCII 'c'.

But it doesn't need to, so long as the compiler translates both L'c'
and 'c' from the multibyte (10646) characters into the same numeric
code values for the resulting char-piece-of-an-int and wchar_t, and
the stdio functions when dealing with text streams provide a similar
mapping (to make the external forms of text streams maximally useful).

There is certainly no requirement in the C standard that 'c' be
represented using the ASCII code set.