Date: Sat, 17 Jan 2004 09:19:28 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: Tim Kientzle <kientzle@acm.org> Cc: Mike Barcroft <mike@FreeBSD.org> Subject: Re: __restrict__ vs __restrict ? Message-ID: <20040117171928.GB38009@dragon.nuxi.com> In-Reply-To: <4008B3F9.6010903@acm.org> References: <40088E75.5080908@acm.org> <20040117015809.GJ9410@FreeBSD.org.ua> <4008B3F9.6010903@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 16, 2004 at 08:03:05PM -0800, Tim Kientzle wrote: > >No, we should be using the __restrict as coded. But I wonder why > >we can't just use "restrict"... > > Because that would really mess up any user program that used > 'restrict' as a variable or function name. I think the > current approach is the best. Such code isn't portable to C99, which is still a goal of ours. I like RU's suggestion, because it is straight C[99] code and not an abstraction. I'll do a 'make world' test and see if we'd have trouble with RU's form. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040117171928.GB38009>