Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!paperboy!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: wchar_t values
Message-ID: <15663@smoke.brl.mil>
Date: 1 Apr 91 13:54:14 GMT
References: <990@sranha.sra.co.jp> <15640@smoke.brl.mil> <1991Apr1.065249.25920@tkou02.enet.dec.com>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 15

In article <1991Apr1.065249.25920@tkou02.enet.dec.com> diamond@jit345.enet@tkou02.enet.dec.com (Norman Diamond) writes:
-In article <15640@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes:
->In article <990@sranha.sra.co.jp> erik@sra.co.jp (Erik M. van der Poel) writes:
->>Which of the following two conditions is the correct interpretation of
->>the ANSI C standard:
->>	('c' == L'c')
->>	('c' == ((char) L'c'))
->Neither one, although the first one is close.  The numerical values
->of these two (possibly distinct) integer types shall be the same.
-Huh?  When they have the same numerical value and both are integer types,
-how is it possible for them to not compare equal?

My point was that the correct interpretation of the standard encompasses
more than the specific example.  The example is implied by the standard's
specification, but not vice-versa.  Thus they are not equivalent.