From owner-freebsd-threads@FreeBSD.ORG Tue Jun 17 09:38:04 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9890D37B401 for ; Tue, 17 Jun 2003 09:38:04 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E97B743FAF for ; Tue, 17 Jun 2003 09:38:03 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h5HGbwXh026549; Tue, 17 Jun 2003 12:37:58 -0400 (EDT) Date: Tue, 17 Jun 2003 12:37:58 -0400 (EDT) From: Daniel Eischen X-Sender: eischen@pcnet5.pcnet.com To: Julian Elischer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: zander@mail.minion.de cc: Gareth Hughes cc: threads@freebsd.org cc: 'Daniel Eischen' cc: Andy Ritger Subject: Re: NVIDIA and TLS X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2003 16:38:04 -0000 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