Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Apr 2003 17:03:29 -0400 (EDT)
From:      Daniel Eischen <eischen@pcnet1.pcnet.com>
To:        Julian Elischer <julian@elischer.org>
Cc:        threads@freebsd.org
Subject:   Re: libkse -> libpthreads
Message-ID:  <Pine.GSO.4.10.10304211648320.9976-100000@pcnet1.pcnet.com>
In-Reply-To: <Pine.BSF.4.21.0304211341050.86193-100000@InterJet.elischer.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.10.10304211648320.9976-100000>