Article View: comp.os.os2
Article #267Re: MSC __STDC__ strange value
From: Doug Gwyn
Date: Tue, 05 Dec 1989 21:42
Date: Tue, 05 Dec 1989 21:42
12 lines
961 bytes
961 bytes
In article <841@megatek.UUCP> hollen@eta.megatek.uucp (Dion Hollenbeck) writes: >By the way, > #define __STDC__ /* evaluates __STDC__ = 0 */ Nope, with this definition a subsequent #if __STDC__ is an illegal program construct. If __STDC__ had been entirely undefined (rather than defined as an empty sequence of pp-tokens), then it is required to evaluate to 0, although perhaps some older compilers might not understand that and flag the #if as illegal even in that case.
Technical Details
Message-ID:
<11746@smoke.BRL.MIL>Path:
arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!aplcen!haven!adm!smoke!gwynReferences:
<223@bohra.cpg.oz> <841@megatek.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!aplcen!haven!adm!smoke!gwyn From: gwyn@smoke.BRL.MIL (Doug Gwyn) Newsgroups: comp.os.os2,comp.lang.c,comp.std.c Subject: Re: MSC __STDC__ strange value Message-ID: <11746@smoke.BRL.MIL> Date: 5 Dec 89 21:42:39 GMT References: <223@bohra.cpg.oz> <841@megatek.UUCP> Reply-To: gwyn@brl.arpa (Doug Gwyn) Followup-To: comp.os.os2 Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 12