Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!uakari.primate.wisc.edu!aplcen!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.std.c
Subject: Re: sizeof in 36-bits machines
Message-ID: <11321@smoke.BRL.MIL>
Date: 17 Oct 89 05:33:12 GMT
References: <272@ssp1.idca.tds.philips.nl> <11284@smoke.BRL.MIL> <398@cpsolv.UUCP> <11300@smoke.BRL.MIL> <14904@haddock.ima.isc.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <14904@haddock.ima.isc.com> karl@haddock.ima.isc.com (Karl Heuer) writes:
>>>Alternatively, you could just make sizeof(int)=sizeof(char)=1
>It remains to be seen whether this is legal, and if so, what happens when the
>input stream contains a bit pattern that compares equal to the value of EOF.

There wouldn't be a problem for the characters corresponding to the C
source character set.  There certainly might be for other characters.
I think our tentative resolution of this was that it IS a permitted
implementation, although there was some question as to whether X3J11
had actually intended for it to be.  Thus it should be raised as a
formal request for interpretation, in order to get a definitive ruling.