Date: Tue, 22 Apr 2003 00:54:37 +0300 (EEST) From: Narvi <narvi@haldjas.folklore.ee> To: Daniel Eischen <eischen@pcnet1.pcnet.com> Cc: Julian Elischer <julian@elischer.org> Subject: Re: libkse -> libpthreads Message-ID: <20030422004324.I29990-100000@haldjas.folklore.ee> In-Reply-To: <Pine.GSO.4.10.10304211648320.9976-100000@pcnet1.pcnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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).
>
Solaris libthr is not a 1:1 thread library - the difference between
libpthread and libthread is that libthread implements UI (sometimes also
called Solaris) threads, and not pthreads.
> I would object to libpthread{M1,MM,MN}. We already
> had a name for libpthread. Libthr can live fine as
> libthr or libthread.
>
No - if both provide the same API with potentially different
implementation tradeoffs, then ythe libraries should be installed with
different names and a symlink to the prefered one installed.
At least for the moment it is not clear that one of teh libraries is a
winner and will eliminate the other, so it would be evil to force people
to explicitly link against one or the other causing future compatibility
problems. Both provide the same pthreads API so there is no reasonable
case for demanding that one of them can't have its SONAME be
libpthpread.so.1
> --
> Dan Eischen
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030422004324.I29990-100000>