Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!ucsd!orion.cf.uci.edu!oberon!stromboli.usc.edu!english
From: english@stromboli.usc.edu (Joe English)
Newsgroups: comp.std.c
Subject: Re: __STDC__ and non-strictly conforming ANSI C compilers
Summary: defined not defined?
Message-ID: <14179@oberon.USC.EDU>
Date: 21 Dec 88 04:25:32 GMT
References: <3236@pegasus.ATT.COM> <9167@smoke.BRL.MIL> <1988Dec15.183822.2559@utzoo.uucp> <22765@watmath.waterloo.edu>
Sender: news@oberon.USC.EDU
Reply-To: english@stromboli.usc.edu (Joe English)
Distribution: na
Organization: University of Southern California, Los Angeles, CA
Lines: 17



In article <22765@watmath.waterloo.edu> rbutterworth@watmath.waterloo.edu (Ray Butterworth) writes:

>The only thing that is guaranteed is that "#if !defined(__STDC__)"
>will guarantee that the compiler is NOT an ANSI Standard C compiler.
>

True, since the "defined" directive does not exist in many pre-dpANS
compilers and will cause an error!

I'm still unclear on the meaning of __STDC__... does it mean
"supports prototypes, void, signed, etc.," or "strictly conforming,
no extensions?"  Or is this not specified?  


--Joe English
english@lipari.usc.edu