Date: Tue, 17 Jun 2003 12:37:58 -0400 (EDT) From: Daniel Eischen <eischen@vigrid.com> To: Julian Elischer <julian@elischer.org> Cc: Andy Ritger <ARitger@nvidia.com> Subject: Re: NVIDIA and TLS Message-ID: <Pine.GSO.4.10.10306171219530.17205-100000@pcnet5.pcnet.com> In-Reply-To: <Pine.BSF.4.21.0306162304070.5566-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Jun 2003, Julian Elischer wrote: > Terry, don't go overboard.. Pleast let him. If it's not too cold, I'll join him for a swim :-) > On Mon, 16 Jun 2003, Terry Lambert wrote: > > > Gareth Hughes wrote: > > > On Mon, 16 Jun 2003, Daniel Eischen wrote: > > > > Right. It just seems wrong to me to be able to insert __thread > > > > after every global variable in a library and instantly make > > > > it thread-safe. > > > > > > Why, exactly? Surely, from a programming point of view, this is > > > exactly what you want -- a transparent way to access your thread > > > local data. >From a programming view, I want well thought APIs. If you are providing a library, its interfaces should be thread-safe by default. I understand that the OpenGL API is what it is, but that shouldn't stop folks from improving on it. > > > > No, what you want first and foremost is your code to compile and > > run on all platforms, without limiting your market by relying on > > defacto language extensions that have not been explicitly and > > intentionally standardized by a recognized standards body. And perhaps someone will get the urge to design an API that is thread-safe and works on all platforms without performance penalties, and this becomes a defacto API. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10306171219530.17205-100000>