From:	noer AT cygnus DOT com (Geoffrey Noer)
Subject:	Pthreads and cygwin32
9 Jul 1998 00:05:06 -0700 :
Message-ID:	<19980709065934.B8014.cygnus.cygwin32.developers@cygnus.com>
Mime-Version:	1.0
To:	cygwin32-developers AT cygnus DOT com

An engineer at Cygnus wrote in part:
>
> I see I might have something here which you guys might want -- I wrote a
> POSIX threads wrapper around Win32 threads that provided a maximal set of
> the POSIX API.
>
> Unfortunately, I didn't keep the code because I wrote it in my spare time
> and then gave it to my old employer for their product.  But I know how I
> did it, so I could rewrite it with ease.  Actually, I could probably write
> it better. :-)
>
> Would this code go into the Cygwin DLL or as another separate pthreads DLL
> to model the typical libpthread.so approach used on UNIX systems?

Personally, I am not sure.  It is a possibility that multi-thread
safety will get addressed in the next few months if certain
possibilities go the way I hope they do.  So it might make sense to
try to add pthreads emulation at the same time.

Assuming we want to add pthreads support (I think we should, assuming
it isn't *too* hard), my preference would be to have it go in a
separate DLL.  I haven't researched pthreads but it's possible that
the calls have to be closely knit to the signals layer in cygwin.dll
or some such thing in which case we might realistically be forced to
add it to the cygwin.dll.

Does anyone know?

--
Geoffrey Noer
noer AT cygnus DOT com

- Raw text -