Path: utzoo!attcan!uunet!auspex!guy
From: guy@auspex.UUCP (Guy Harris)
Newsgroups: comp.std.c
Subject: Re: __STDC__ and non-conforming ANSI C compilers
Message-ID: <866@auspex.UUCP>
Date: 19 Jan 89 00:57:53 GMT
References: <9391@smoke.BRL.MIL> <8731@megaron.arizona.edu> <9405@smoke.BRL.MIL> <860@auspex.UUCP>
Reply-To: guy@auspex.UUCP (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 26

In article <860@auspex.UUCP> guy@auspex.UUCP (Guy Harris) demonstrates
that one should not operate heavy machinery while drowsy, by writing:

>How meaningful is its antithesis? "Strict ANSI non-compliance" could
>mean anything from "they define 'ferror' as a macro in <stdio.h>" to
				  ^^^^^^

when he meant

>mean anything from "they define 'fileno' as a macro in <stdio.h>" to
				  ^^^^^^

and writing

>include file also mentioned in ANSI C.  For instance, <stdio.h> would
>probably define "ferror" as a macro.  Doing so breaks ANSI compliance,
		  ^^^^^^

when he meant

>probably define "fileno" as a macro.  Doing so breaks ANSI compliance,
		  ^^^^^^

since "ferror" is part of ANSI C's name space, but "fileno" isn't but
*is* part of POSIX's name space (and is defined as a macro in all the
UNIX implementations I know of).  Sigh.