Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!brl-adm!brl-smoke!smoke!tweten@AMES-PRANDTL.ARPA
From: tweten@AMES-PRANDTL.ARPA (Dave Tweten)
Newsgroups: net.lang.c
Subject: Re: Signed char - What Foolishness Is This!
Message-ID: <4766@brl-smoke.ARPA>
Date: Mon, 20-Oct-86 19:16:27 EDT
Article-I.D.: brl-smok.4766
Posted: Mon Oct 20 19:16:27 1986
Date-Received: Wed, 22-Oct-86 03:21:47 EDT
Sender: news@brl-smoke.ARPA
Lines: 22

From: Brent Chapman <chapman@cory.berkeley.edu>

	In article <8719@duke.duke.UUCP> jwg@duke.UUCP (Jeffrey William Gillette) writes:
	>MSC 4.0 defaults 'char' to 'signed char'.  

	[ it defaulted to 'unsigned char' in previous versions of MSC -- Brent]

My, are we confused!  As it turns out, Microsoft C version 3.0 defaulted
char to signed char, and version 4.0 defaults it to unsigned, exactly
the opposite of the claimed situation.  I can't quote the version 4.0
manual (it's at home), but the version 3.0 "Language Reference" manual
says (on page 46):

	Type		Storage		Range of Values (Internal)
			.
			.
			.
	char		1 byte		-128 to 127
			.
			.
			.
	unsigned char	1 byte		0 to 255