From owner-freebsd-standards  Wed Aug  7 23:59:12 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 AFD0237B400; Wed,  7 Aug 2002 23:59:10 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 936AF43E5E; Wed,  7 Aug 2002 23:59:09 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102])
	by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id QAA17757;
	Thu, 8 Aug 2002 16:58:40 +1000
Date: Thu, 8 Aug 2002 17:03:29 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: "M. Warner Losh" <imp@bsdimp.com>
Cc: pfeifer@dbai.tuwien.ac.at, <obrien@FreeBSD.ORG>,
	<freebsd-standards@FreeBSD.ORG>
Subject: Re: MFCing stdlib.h and stddef.h
In-Reply-To: <20020807.102449.122462505.imp@bsdimp.com>
Message-ID: <20020808165908.N8452-100000@gamplex.bde.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-standards@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-standards.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-standards>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-standards>
X-Loop: FreeBSD.ORG

On Wed, 7 Aug 2002, M. Warner Losh wrote:

> ...
> 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?

-current has a temporary fix for this in rev.1.46 of <sys/cdefs.h> and
associated changes.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-standards" in the body of the message