From owner-freebsd-threads@FreeBSD.ORG Mon Apr 21 14:31:43 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 571D937B401 for ; Mon, 21 Apr 2003 14:31:43 -0700 (PDT) Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5D2343F3F for ; Mon, 21 Apr 2003 14:31:42 -0700 (PDT) (envelope-from julian@elischer.org) Received: from interjet.elischer.org (12-232-168-4.client.attbi.com[12.232.168.4]) by sccrmhc01.attbi.com (sccrmhc01) with ESMTP id <200304212131410010084q43e>; Mon, 21 Apr 2003 21:31:41 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id OAA86354; Mon, 21 Apr 2003 14:31:40 -0700 (PDT) Date: Mon, 21 Apr 2003 14:31:38 -0700 (PDT) From: Julian Elischer To: Daniel Eischen In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org Subject: Re: libkse -> libpthreads 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: Mon, 21 Apr 2003 21:31:43 -0000 On Mon, 21 Apr 2003, Daniel Eischen wrote: > On Mon, 21 Apr 2003, Julian Elischer wrote: > > > > > WE have a small problem.. when we started we had only on pthreads > > package and libKSE was teh heir.. > > No, libkse WAS libpthread. We renamed the library > temporarily until it was proven to work reasonably > well (I did the commit that renamed it). > > > now we have to live with libthr in the picture. > > it is possible that we should think of a naming scheme that > > allows all 3 libraries to have meaningful related names > > > > libc_r -> libpthreadM1 > > libthr -> libpthreadMM > > libkse -> libpthreadMN > > > > or something. > > The current naming scheme is fine. Libc_r is already > a well known name along with its shortcomings. Solaris > uses libthread for 1:1 as far as I can tell which would > seem to match libthr, and libpthread is the POSIX threads > library whose goal is to support POSIX as fully as > possible (scope process and scope system). > > I would object to libpthread{M1,MM,MN}. We already > had a name for libpthread. Libthr can live fine as > libthr or libthread. > > -- > Dan Eischen > > fair enough