Xref: utzoo comp.os.os2:352 comp.lang.c:24375 comp.std.c:2250
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!sun-barr!lll-winken!arisia!leisner
From: leisner@arisia.Xerox.COM (Marty Leisner)
Newsgroups: comp.os.os2,comp.lang.c,comp.std.c
Subject: Re: MSC __STDC__ strange value
Message-ID: <4714@arisia.Xerox.COM>
Date: 7 Dec 89 22:33:14 GMT
References: <223@bohra.cpg.oz> <9692@pyr.gatech.EDU>
Reply-To: leisner@arisia.UUCP (Marty Leisner)
Organization: Xerox Palo Alto Research Center
Lines: 19

In article <9692@pyr.gatech.EDU> is813cs@pyr.gatech.edu (Cris Simpson) writes:
>   According to K&R2, (pg 233), __STDC__ must be defined, as well as
>(insert your own __ 's)  LINE, FILE, DATE, TIME.   However, since
>5.1 is not ANSI, __STDC__ can't be 1.
>

__STDC__ only needs to be defined in a conforming compiler.

It makes no sense to define __STDC__ to be 0 (except to confuse everyone).

I work with a TI34010 and the TI supplied C compiler also defines __STDC__ to 0.  At least with MSC, that's trying to be an ansi C compiler.  TI only claims to be a
K&R C compiler, if that much.

This STDC == 0 stuff has caused  nothing but grief.

I'm close to the point to patching the preprocessor binary to remove this nonsense.


marty leisner
leisner.henr@xerox.com