Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!wuarchive!sdd.hp.com!mips!cs.uoregon.edu!ogicse!intelhf!ichips!iwarp.intel.com!inews!bishop!bhoughto
From: bhoughto@bishop.intel.com (Blair P. Houghton)
Newsgroups: comp.lang.c
Subject: Re: 0xFF != '\xFF' ?
Message-ID: <3907@inews.intel.com>
Date: 19 Apr 91 04:38:08 GMT
References: <wolfram.671457062@cip-s08> <H7Yd2E@ppcger.ppc.sub.org> <wolfram.671964442@cip-s02>
Sender: news@inews.intel.com
Organization: Intel Corp, Chandler, AZ
Lines: 14

In article <wolfram.671964442@cip-s02> wolfram@cip-s02.informatik.rwth-aachen.de (Wolfram Roesler) writes:
>Sepp@ppcger.ppc.sub.org (Josef Wolf) writes:
>>You even don't know about the number of bits of a char (or is it defined?)
>>So you can get into trouble with this.
>
>A char is defined to contain a single character, so this is usually 8 bits.

Look in <limits.h> (or grep through your compiler's include-files)
for `CHAR_BIT'.  This is the definition of the number of bits
in a `char'.

				--Blair
				  "Give me egrep and a place to
				   stand and I will move the earth."