From owner-freebsd-hackers@FreeBSD.ORG Mon Jan 19 11:20:00 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE55F16A4CF; Mon, 19 Jan 2004 11:20:00 -0800 (PST) Received: from phantom.cris.net (phantom.cris.net [212.110.130.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B4F043D5E; Mon, 19 Jan 2004 11:19:57 -0800 (PST) (envelope-from ru@FreeBSD.org.ua) Received: from phantom.cris.net (ru@localhost [127.0.0.1]) by phantom.cris.net (8.12.10/8.12.10) with ESMTP id i0JJKOjm049256; Mon, 19 Jan 2004 21:20:25 +0200 (EET) (envelope-from ru@FreeBSD.org.ua) Received: (from ru@localhost) by phantom.cris.net (8.12.10/8.12.10/Submit) id i0JJKOYN049247; Mon, 19 Jan 2004 21:20:24 +0200 (EET) (envelope-from ru) Date: Mon, 19 Jan 2004 21:20:24 +0200 From: Ruslan Ermilov To: "David O'Brien" , Harti Brandt Message-ID: <20040119192023.GB48928@FreeBSD.org.ua> References: <40088E75.5080908@acm.org> <20040117015809.GJ9410@FreeBSD.org.ua> <4008B3F9.6010903@acm.org> <20040117171928.GB38009@dragon.nuxi.com> <20040119143913.Y42652@beagle.fokus.fraunhofer.de> <20040119161719.GB4587@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CUfgB8w4ZwR/yMy5" Content-Disposition: inline In-Reply-To: <20040119161719.GB4587@dragon.nuxi.com> User-Agent: Mutt/1.5.5.1i cc: hackers@FreeBSD.org Subject: Re: __restrict__ vs __restrict ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2004 19:20:01 -0000 --CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 19, 2004 at 08:17:19AM -0800, David O'Brien wrote: > On Mon, Jan 19, 2004 at 02:41:26PM +0100, Harti Brandt wrote: [...] > > What about third party code that reads cdefs.h and is pre-c99? It's > > perfectly ok to use restrict as a name there. >=20 > Its also perfectly OK to use 'exp' as a varible, but we've been getting > rid of those because they are difficult to deal with. The same is true > of older C++ code when new reserved words were added. Sometimes one has > to move forward to the modern world. This is all congecture -- can you > find one thing in /usr/ports that uses restrict as a symbol? >=20 This is not the point. The point was if we want to stay C89 compatible or not. If we decide at some point that FreeBSD should no longer accept valid C89 code, this change is probably ok. If we decide now that our kernel should be C99 clean, we should compile it with -std=3Dc99, and replace all `__restrict''s in not headers with C99 `restrict's. Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFADC33Ukv4P6juNwoRAjdWAJ9dPU0oJukM2QXGUUSkihb81syhVQCgiSqM 78bhQ6woRhh7MBbx5A+/kvI= =ZIsD -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5--