__STDC__ and non-conforming ANSI C compilers
Guy Harris
guy at auspex.UUCP
Thu Jan 19 10:57:53 AEST 1989
In article <860 at auspex.UUCP> guy at 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.
More information about the Comp.std.c
mailing list