Article View: comp.std.c
Article #2452Re: Want the word on __STDC__
From: Doug Gwyn
Date: Wed, 20 Feb 1991 00:53
Date: Wed, 20 Feb 1991 00:53
14 lines
1054 bytes
1054 bytes
In article <4755@lib.tmc.edu> dfenyes@thesis1.hsch.utexas.edu (David Fenyes) writes: >The question is: Does an ANSI cpp ALWAYS #define __STDC__, even if it >is used intentionally with a K&R compiler (#defined to 0)? It does whatever it does. The C standard constrains only conforming implementations, which must in effect predefine __STDC__ to 1. Non-conforming implementations are outside the scope of the standard. Having said that, I would add that implementors who #define __STDC__ to anything at all in non-conforming variants of their compilers are not doing anyone a favor, and I wish they would desist from that practice.
Technical Details
Message-ID:
<15260@smoke.brl.mil>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!adm!smoke!gwynReferences:
<4755@lib.tmc.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!adm!smoke!gwyn From: gwyn@smoke.brl.mil (Doug Gwyn) Newsgroups: comp.std.c Subject: Re: Want the word on __STDC__ Keywords: ANSI C __STDC__ preprocessor Message-ID: <15260@smoke.brl.mil> Date: 20 Feb 91 00:53:34 GMT References: <4755@lib.tmc.edu> Organization: U.S. Army Ballistic Research Laboratory, APG, MD. Lines: 14