Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!wuarchive!mit-eddie!uw-beaver!zephyr.ens.tek.com!tektronix!reed!minar From: minar@reed.bitnet (Nelson Minar,L08,x640,7776519) Newsgroups: comp.sys.apollo Subject: Re: How ANSI is Apollo's cc 6.7 (SR 10.2) Message-ID: <15444@reed.UUCP> Date: 12 Sep 90 04:46:41 GMT References: <15434@reed.UUCP> <847@usage.csd.unsw.oz.au> <1810@tuvie> Sender: news@reed.UUCP Reply-To: minar@reed.bitnet (Nelson Minar) Organization: Reed College, Portland, OR Lines: 10 In article <1810@tuvie> hp@vmars.tuwien.ac.at (Peter Holzer) writes: >cameron@usage.csd.oz (Cameron Simpson,Uhmmm..???? Who knows) writes: >Not on 10.2. __STDC__ is defined as 1. >[host of things that don't work according to ANSI] 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?