Date: Thu, 8 Aug 2002 17:03:29 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> 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 Message-ID: <20020808165908.N8452-100000@gamplex.bde.org> In-Reply-To: <20020807.102449.122462505.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020808165908.N8452-100000>