From owner-freebsd-hackers Mon Aug 9 9: 0: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id BA6C314BF1 for ; Mon, 9 Aug 1999 09:00:02 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id LAA63032; Mon, 9 Aug 1999 11:56:32 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Mon, 9 Aug 1999 11:56:32 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Tony Finch Cc: hackers@FreeBSD.org Subject: Re: quad_t and portability In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 9 Aug 1999, Tony Finch wrote: > "Brian F. Feldman" wrote: > > > >Is there anyone who is specifically checking for long long > >C9X-compliancy in the source tree (mainly libc)? > > I started reviewing libc for C9X features in general -- a fair amount > of work is required to update macros and typedefs in > (plus the new ). Shall we work on it, then? > > Doing a thorough job is difficult because C9X is somewhat gratuitously > incompatible with gnu C (e.g. the spelling of __complex__, zero-length > arrays in structures, macro varargs, etc.) and gnu C doesn't yet > support restrict. But GNU has officially stated that they will fully support C9X, and they've started already. For instance, int *a = ((int [4]){1,2,3,4}); should work now, according to the infopages. Eventually, I'd be certain that GNU would rather be compliant with C9X than with GNU C. > > Tony. > -- > f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message