Xref: utzoo comp.sys.atari.st:16725 comp.std.c:1224
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!ames!xanth!ukma!uflorida!novavax!twwells!bill
From: bill@twwells.uucp (T. William Wells)
Newsgroups: comp.sys.atari.st,comp.std.c
Subject: Re: Mark Williams C
Message-ID: <1000@twwells.uucp>
Date: 27 May 89 18:40:19 GMT
References: <24094@agate.BERKELEY.EDU> <431fba10.14a1f@gtephx.UUCP> <8137@boring.cwi.nl> <8530@chinet.chi.il.us> <13475@haddock.ima.isc.com>
Reply-To: bill@twwells.UUCP (T. William Wells)
Organization: None, Ft. Lauderdale
Lines: 25
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

In article <13475@haddock.ima.isc.com> karl@haddock.ima.isc.com (Karl Heuer) writes:
: But not nearly as reasonable as undefining it completely, which would work
: with *both* "#if" and "#ifdef", and which would be consistent with all the
: compilers that were written before X3J11 invented the __STDC__ symbol.

The ANSI standard applies only to implementations and programs
claiming conformance to it. Who should care what others do? If you
are writing programs that have to check the implementation for
conformance, you had just better only check for __STD__ == 1.
Anything else is just damn lazyness on your part.

If you are writing code that has to deal with preprocessors that will
complain about #if __STDC__ == 1 when __STDC__ is undefined, add this
to the top of your code:

	#ifndef __STDC__
	#define __STDC__ 0
	#endif

Then wherever you need to test for ANSI conformance, you can just
test for __STDC__ == 1 without worrying about __STDC__ being
undefined at that point.

---
Bill                            { uunet | novavax } !twwells!bill