Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site umcp-cs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!amdcad!lll-crg!gymble!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.lang.c
Subject: Re: type cast in initializer
Message-ID: <2950@umcp-cs.UUCP>
Date: Thu, 30-Jan-86 13:50:36 EST
Article-I.D.: umcp-cs.2950
Posted: Thu Jan 30 13:50:36 1986
Date-Received: Sat, 1-Feb-86 05:52:47 EST
References: <302@hsi.UUCP>
Distribution: net
Organization: U of Maryland, Computer Science Dept., College Park, MD
Lines: 21

In article <302@hsi.UUCP> stevens@hsi.UUCP (Richard Stevens) writes:

> I've found the two lines
>	int	x = 0;
>	char	*ptr = (char *) &x;
> acceptable to every C compiler I've used, until running into the
> Whitesmith's C compiler.  They refuse to accept the type coercion
> "(char *)" on the second initialization. ...
>
> I talked to Whitesmiths about this and they are firm that their
> interpretation of the "standard" is that a type coercion following
> the equals sign is not allowed and they don't plan to change their
> compiler.

Whitesmiths has never been one to do reasonable things with their
compiler.  Their interpretation is bogus.  How a company can be
so simultaneously good and bad at what they do is just amazing.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1415)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu