Path: utzoo!attcan!utgpu!watserv1!watmath!rbutterworth
From: rbutterworth@watmath.waterloo.edu (Ray Butterworth)
Newsgroups: comp.os.os2
Subject: Re: MSC __STDC__ strange value
Message-ID: <32453@watmath.waterloo.edu>
Date: 8 Dec 89 17:03:27 GMT
References: <223@bohra.cpg.oz> <11744@smoke.BRL.MIL>
Reply-To: rbutterworth@watmath.waterloo.edu (Ray Butterworth)
Organization: U. of Waterloo, Ontario
Lines: 19

In article <11744@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
>In article <223@bohra.cpg.oz> ejp@bohra.cpg.oz (Esmond Pitt) writes:
>>For some strange reason, the MSC 5.1 compiler defines __STDC__ as 0 ...
>>Why?
>
>Some C compiler vendors seem to think that they're doing the programmer
>a favor by predefining __STDC__ to a non-1 value to indicate that their
>compiler has "some" standard features but not full compliance.
>However, since there is no way to tell just what part of the Standard is
>conformed to and what part isn't, such non-standard predefinition of
>__STDC__ is not very useful and, as you seem to have discovered, can
>actually get in the way of the programmer.

Everyone should submit a bug report to their favourite compiler vendor
that their preprocessor doesn't also predefine:
#define vax 0
#define unix 0
#define pdp11 0
...