Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!nosc!ucsd!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.std.c
Subject: Re: __STDC__ and non-conforming ANSI C compilers
Message-ID: <9454@smoke.BRL.MIL>
Date: 20 Jan 89 16:17:35 GMT
References: <9369@smoke.BRL.MIL> <2788@mhres.mh.nl> <9392@smoke.BRL.MIL> <9416@smoke.BRL.MIL> <2797@ficc.uu.net> <9437@smoke.BRL.MIL> <398@jhereg.Jhereg.MN.ORG>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 12

In article <398@jhereg.Jhereg.MN.ORG> mark@jhereg.MN.ORG (Mark H. Colburn) writes:
>By the same token, the user could specify -D__STDC__ on the command line
>to the C compiler.  That would not necessarily make the compiler being
>used an ANSI C conforming compiler...

In fact, this seems like a good way for users on nonconforming
implementations that have a lot of so-called "ANSI C" features
to avail himself of them.  It's his responsibility for limiting
his program's use of __STDC__ to access just features the
nonconforming implementation actually provides.  That's much
better than the implementation unconditionally pretending to be
something it's not.