Article View: comp.std.c
Article #5599Re: __STDC__ and non-conforming ANSI C compilers
From: Mike Coffin
Date: Tue, 17 Jan 1989 22:37
Date: Tue, 17 Jan 1989 22:37
13 lines
1066 bytes
1066 bytes
From article <358@masscomp.UUCP>, by ftw@masscomp.UUCP (Farrell Woods):
> If I invoke a conforming compiler with "cc -DFOO", but my program
> has #ifdef __STDC__ in it, how does this break conformance?
If "cc -DFOO" has the effect of providing of predefining FOO, then it
does not provide a conforming compilation environment: the program's
name space has been polluted. So I assume that __STDC__ will not be
defined in such cases. Do you think this should be an exception? If
so, do you have any other exceptions in mind?
--
Mike Coffin mike@arizona.edu
Univ. of Ariz. Dept. of Comp. Sci. {allegra,cmcl2}!arizona!mike
Tucson, AZ 85721 (602)621-2858
Technical Details
Message-ID:
<8742@megaron.arizona.edu>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!ncis!helios.ee.lbl.gov!pasteur!agate!bionet!ig!arizona!mikeReferences:
<358@masscomp.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!ncis!helios.ee.lbl.gov!pasteur!agate!bionet!ig!arizona!mike From: mike@arizona.edu (Mike Coffin) Newsgroups: comp.std.c Subject: Re: __STDC__ and non-conforming ANSI C compilers Message-ID: <8742@megaron.arizona.edu> Date: 17 Jan 89 22:37:47 GMT References: <358@masscomp.UUCP> Organization: U of Arizona CS Dept, Tucson Lines: 13