Path: utzoo!utgpu!watserv1!watmath!att!occrsh!uokmax!apple!usc!wuarchive!uunet!mcsun!tuvie!vmars!hp
From: hp@vmars.tuwien.ac.at (Peter Holzer)
Newsgroups: comp.sys.apollo
Subject: Re: How ANSI is Apollo's cc 6.7 (SR 10.2)
Message-ID: <1810@tuvie>
Date: 11 Sep 90 17:18:53 GMT
References: <15434@reed.UUCP> <847@usage.csd.unsw.oz.au>
Sender: news@tuvie
Lines: 32

cameron@usage.csd.oz (Cameron Simpson,Uhmmm..???? Who knows) writes:

>The tech rep is wrong. I think the documentation says evasive things like
>"many ANSI extensions" and so forth. You'll discover that their definition
>of __STDC__ is also evasive - they define it to 0.

Not on 10.2. __STDC__ is defined as 1.

>| I wouldn't care about the compiler as I have gcc running on the machine.
>| However, I have to use the header files that came with the machine, and here
>| is where I have a problem.  [...]
>|         unsigned char   *_ptr #attribute[aligned(1)];

>On the subject of the semiANSIness of the Apollo cc, peering at my
>a configuration file I have here the following weirdness applied under 10.1.
>I think most of them still apply under 10.2 (we run it but I haven't checked).
>	- "const" doesn't work.
>	- the ANSI #include files aren't there (limits.h and so forth).
>	- self-referential macros fail, viz
>		#define	it(x)	(fputs("hi\n",stderr),it(x))
>	- stdio isn't ANSI. Supposedly fflush(NULL) will flush all streams.
>	  Not on Apollos.

Add:
	- "signed char" doesn't work.
	- stdargs don't work either.

--
|    _	| Peter J. Holzer			| Think of it	|
| |_|_)	| Technische Universitaet Wien		| as evolution	|
| | |	| hp@vmars.tuwien.ac.at			| in action!	|
| __/  	| ...!uunet!mcsun!tuvie!vmars!hp	|     Tony Rand	|