Path: utzoo!attcan!uunet!samsung!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: <1990Sep12.133121@pisa.ifs.umich.edu>
Date: 12 Sep 90 17:35:14 GMT
References: <15434@reed.UUCP> <847@usage.csd.unsw.oz.au> <1810@tuvie> <15444@reed.UUCP>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 10

In article <15444@reed.UUCP>, minar@reed.bitnet (Nelson Minar,L08,x640,7776519) writes:
  So why does the Apollo C compiler define __STDC__ to be 1, thus signaling to
  the world "Hey! We're an ANSI C compiler!"  Is this just a sick joke, or the
  result of bad testing from the compiler shop, or an honest misunderstanding of
  what it means to be ANSI? Or is it just patently broken?

My understanding is that this is historical.  __STDC__ was originally turned
on back when the only thing it meant was "function prototypes."  (This would
have been about two or three years ago.)  As actual code started using more
of the ANSI features, the compiler didn't keep up.