From owner-freebsd-standards Wed Aug 7 9:53:17 2002 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 016EB37B400; Wed, 7 Aug 2002 09:53:16 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id A24A343E72; Wed, 7 Aug 2002 09:53:14 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.5/8.12.3) with ESMTP id g77Gr39R079077; Wed, 7 Aug 2002 10:53:04 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 07 Aug 2002 10:24:49 -0600 (MDT) Message-Id: <20020807.102449.122462505.imp@bsdimp.com> To: pfeifer@dbai.tuwien.ac.at Cc: obrien@FreeBSD.ORG, freebsd-standards@FreeBSD.ORG Subject: Re: MFCing stdlib.h and stddef.h From: "M. Warner Losh" In-Reply-To: <20020807.094128.60713184.imp@bsdimp.com> References: <20020720.124158.82192188.imp@bsdimp.com> <20020807.094128.60713184.imp@bsdimp.com> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Done. I've committed the fixes. PR 40402 is interesting and brings to light a small problem. C++ does not define long long that I could find (granted, I only have Stroustrup's books, and not the actual standard). Therefore the warnings about long long not being in c++ are correct and valid. stdtoll is what is triggering them. It is required to be in stdlib.h by ISO-C99 (S 7.20.1.3 #1 and B.19). Ditto atoll. g++, and I think most other modern C++ compilers, supports long long as an extension to the language. -pedantic turns these extensions off (or at least warns about them). I'm not sure what we can do about that. Since the compiler is correctly flagging an extension, I closed the bug. I'm not sure what to do about this disconnect between C++ and C standards. Comments from the standards@ people? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message