Date: Sat, 10 Nov 2001 12:15:12 -0500 (EST) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Jens Schweikhardt <schweikh@schweikhardt.net> Cc: freebsd-current@FreeBSD.ORG Subject: Re: malloc.h Message-ID: <200111101715.fAAHFCB62127@khavrinen.lcs.mit.edu> In-Reply-To: <20011110145222.A942@schweikhardt.net> References: <200111080839.fA88dv740802@harmony.village.org> <200111080950.fA89oIk21059@gits.dyndns.org> <20011108225915.A75044@uriah.heep.sax.de> <20011110145222.A942@schweikhardt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Sat, 10 Nov 2001 14:52:22 +0100, Jens Schweikhardt <schweikh@schweikhardt.net> said: > As I understand it, the only problem is if some implementation indicates > non-conformance with #define __STDC__ 0, which is unheard of to me, and, > if I were an implementor of such a system, I'd just leave it undefined. That is a slight misinterpretation of what those systems do. Those systems have a three-mode compiler (similar to GCC in that regard). When running in `traditional' mode, they do not define __STDC__. When running in `strict ANSI/ISO' mode, they define __STDC__ to unity, as required by the Standard. When running in their default mode, which accepts a proper superset of the ANSI/ISO language, they define __STDC__ to be zero. The theory is that only conformance tests would ever actually care about the exact value of __STDC__. None of this has anything to do with us, since the Standard Header Files are part of The Implementation, and FreeBSD doesn't use one of those (MIPS or DECpaq) compilers. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111101715.fAAHFCB62127>