Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!sdd.hp.com!decwrl!bacchus.pa.dec.com!shlump.nac.dec.com!tkou02.enet.dec.com!diamond
From: diamond@tkou02.enet.dec.com (diamond@tkovoa)
Newsgroups: comp.std.c
Subject: Re: Multibyte character constants????
Keywords: Hackers of the world, unite!
Message-ID: <1826@tkou02.enet.dec.com>
Date: 30 Jun 90 02:36:46 GMT
References: <1990Jun28.221927.6823@idt.unit.no> <1824@tkou02.enet.dec.com>
Reply-To: diamond@tkou02.enet.dec.com (diamond@tkovoa)
Organization: Digital Equipment Corporation Japan , Tokyo
Lines: 25

In article <1990Jun28.221927.6823@idt.unit.no> arnej@solan1.solan.unit.no writes:
>>We have stumbled across the subject of multibyte character
>>constants.  Is this defined anywhere?
>>For example, if we say
>>main(){printf("%d\n",'AB');}
>>what should the output be?

In article <1824@tkou02.enet.dec.com> I wrote:
>Exactly the opposite.  The standard did not even just leave it undefined
>by saying nothing.  The standard explicitly says that it's undefined.

Sorry, the standard actually says it's implementation defined.
So your vendor's manual does have to say what the compiler does with them.
(I happened to read something else in TFM that day which was in fact
undefined, and then mixed them up in my memory.  Sorry for misleading
anyone.)

>It does not have to compile.  It does not have to execute.  It it does,
>it can print anything, or exec rogue.

This is still true.  Only, your vendor DOES have to tell you what it will do.
And you still would not use it at all in a portable program.
-- 
Norman Diamond, Nihon DEC     diamond@tkou02.enet.dec.com
This is me speaking.  If you want to hear the company speak, you need DECtalk.