From owner-freebsd-current Sat Nov 10 9:15:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 4EC9A37B419 for ; Sat, 10 Nov 2001 09:15:15 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id fAAHFCB62127; Sat, 10 Nov 2001 12:15:12 -0500 (EST) (envelope-from wollman) Date: Sat, 10 Nov 2001 12:15:12 -0500 (EST) From: Garrett Wollman Message-Id: <200111101715.fAAHFCB62127@khavrinen.lcs.mit.edu> To: Jens Schweikhardt Cc: freebsd-current@FreeBSD.ORG Subject: Re: malloc.h 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> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < 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