Article View: comp.std.c
Article #5593Re: __STDC__ and non-conforming ANSI C compilers
From: Stephen J. Friedl
Date: Mon, 16 Jan 1989 02:39
Date: Mon, 16 Jan 1989 02:39
16 lines
1144 bytes
1144 bytes
In article <8470@edsews.EDS.COM>, charette@edsews.EDS.COM (Mark A. Charette) writes:
> If we could only get them to drop the __STDC__ if the compiler doesn't conform
> to the full-use standards.
Convincing a vendor to simply drop __STDC__=0 is probably harder than
it looks because it will "break" the code of those who bought the compiler
the first time. Perhaps a reasonable compromise is to permit __STDC__
to be #undef-ed (on the command line, perhaps) in non-conformant mode.
Steve
--
Stephen J. Friedl 3B2-kind-of-guy friedl@vsi.com
V-Systems, Inc. I speak for you only attmail!vsi!friedl
Santa Ana, CA USA +1 714 545 6442 {backbones}!vsi!friedl
---------Nancy Reagan on Hawaiian musicians: "Just say Ho"--------
Technical Details
Message-ID:
<1017@vsi.COM>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!vsi!friedlReferences:
<898@ubu.warwick.UUCP> <9369@smoke.BRL.MIL> <8470@edsews.EDS.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!vsi!friedl From: friedl@vsi.COM (Stephen J. Friedl) Newsgroups: comp.std.c Subject: Re: __STDC__ and non-conforming ANSI C compilers Message-ID: <1017@vsi.COM> Date: 16 Jan 89 02:39:17 GMT References: <898@ubu.warwick.UUCP> <9369@smoke.BRL.MIL> <8470@edsews.EDS.COM> Organization: V-Systems, Inc. -- Santa Ana, CA Lines: 16