[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [task #5487] cthreads -> pthreads

From: Neal H. Walfield
Subject: Re: [task #5487] cthreads -> pthreads
Date: Tue, 07 Nov 2006 17:00:06 +0100
User-agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.4 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Tue, 7 Nov 2006 15:36:03 +0100,
Richard Braun wrote:
> On Tue, Nov 07, 2006 at 03:53:02PM +0200, Constantine Kousoulos wrote:
> > That wasn't what i meant. I would like to know what are the major
> > things that *don't* work. Can someone enlighten me on that subject?
> I know ;-). I would also like to know, otherwise I would have told you.
> > Does the current pthread implementation enable the use of pthreads 
> > in new servers-libraries-translators? In other words, can a new 
> > server/translator written with pthreads coexist with the current 
> > cthread-based servers/translators?
> No, translators must use the cthreads library :-/. I guess the main
> reason is that some libraries commonly used by translators, such as
> libports, use the cthreads library internally (e.g. when using
> ports_manage_port_operations_multithread()), which forces translators
> to use compatible objects (like mutexes).

Having two implementations of a function with different parameters and
results is not necessarily bad as long as they are used consistently
and they don't interact poorly with each other.  The latter is quite
difficult to avoid in threading libraries and is why you can't link
both libpthread and libthreads to a single program.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]