Xref: utzoo comp.lang.c:8900 comp.arch:4251
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!bbn!rochester!rutgers!mtunx!whuts!picuxa!gp
From: gp@picuxa.UUCP (Greg Pasquariello X1190)
Newsgroups: comp.lang.c,comp.arch
Subject: Re: Bit Addressable Architectures
Message-ID: <533@picuxa.UUCP>
Date: 4 Apr 88 14:27:59 GMT
References: <11702@brl-adm.ARPA> <243@eagle_snax.UUCP> <2245@geac.UUCP> <1988Mar6.002518.945@utzoo.uucp> <2760@mmintl.UUCP> <17458@watmath.waterloo.edu> <504@sol.warwick.ac.uk> <113@csanta.UUCP>
Reply-To: gp@picuxa.UUCP (Greg Pasquariello X1190)
Organization: AT&T/EDS Product Integration Center
Lines: 17

In article <113@csanta.UUCP> greg@csanta.UUCP (Root) writes:
>Hmm, I'm new on the net here, so excuse me for jumping into the middle of a
>discussion, but sizeof(char) is always 1.  The number of bits in a char
>is a whole 'nuther story.  This is usually 8, but need not be.  This is
>true of both dpANSI C and K&R C.

This is true of the dpANSI C and K&R C _implementation_, but it is not neces-
sarily true of the C definition.  Sizeof yields "the size, in bytes, of it's 
operand" (K&R pg 188).   The fundamental type char, is "large enough to store
any member of the implementations character set" (K&R pg 182).  This _could_
be multiple bytes!


(God I hope what I just said is true :-))

Greg Pasquariello
ihnp4!picuxa!gp