Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: How ANSI is Apollo's cc 6.7 (SR 10.2)
Message-ID: <1990Sep11.125213@pisa.ifs.umich.edu>
Date: 11 Sep 90 17:00:57 GMT
References: <15434@reed.UUCP> <847@usage.csd.unsw.oz.au>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 26

In article <847@usage.csd.unsw.oz.au>, cameron@usage.csd.oz (Cameron Simpson,Uhmmm..???? Who knows) writes:
  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.

The most frequent problem I've run across is that cpp doesn't handle '##'.
You can fix all these problems by using the '-A nansi' flag, which tells the
compiler "don't even pretend to be ANSI compliant."  But that's a pretty big
hammer.  The X imake config file has a switch that says "ANSI C but no '##'."
Sure would be nice if all sources were configurable at such fine grain.

As for stdio, I don't see this as a compiler issue.  I've never even heard
of it before.

  Rumour hath it that 10.3 has an ANSI compiler. That would be nice.
  A better lint would be nice, too.

The compiler has now been decoupled from the OS, or so I hear.  It's always
been a separate installable product.  So there isn't really a "sr10.3
compiler."  But I've also heard that the new compiler will be full ANSI.