From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Medina, Aurelio" <aureliom@crt.com>
To: "'Ross Johnson'" <rpj@ise.canberra.edu.au>
Cc: Pthreads Developers List <pthreads-win32@sourceware.cygnus.com>
Subject: RE: Snapshot 1999-08-12 available
Date: Thu, 02 Sep 1999 07:15:00 -0000
Message-id: <F931488C3634D11180D700A02461E24502035AFB@chitmd03.nt.il.nbgfn.com>
X-SW-Source: 1999/msg00076.html

To whom it may concern,

I have ported the proposed POSIX Read/Write Locks (e.g.
pthread_rwlock_init()) library to Windows NT.  These routines are almost
completely copied from Richard Steven's latest UNIX Network Programming
book.  The library is currently a UNIX98, X/Open standard and available on
HP-UX 11.0.  Also, according to Mr. Stevens, it should soon become a POSIX
standard on all UNIX platforms.  Almost all the software I develop has to
run on both Windows NT and UNIX.  Therefore, I would really like to see
these useful read/write mutex routines in the Pthreads-Win32 library. 

P.S. I'm also working on porting the POSIX Message Queue (e.g. mq_open())
library to Windows NT.  When this is complete, I will send you the source
and header files if interested.


Attached is the source and header file for the POSIX Read/Write Locks.
 <<pthread_rwlock.c>>  <<pthread_rwlock.h>> 

Thanks,
Aurelio Medina
Distributed Systems Management
mailto:aureliom@crt.com < mailto:aureliom@crt.com > 

	-----Original Message-----
	From:	Ross Johnson [SMTP:rpj@ise.canberra.edu.au]
	Sent:	Wednesday, August 11, 1999 10:49 PM
	To:	Pthreads Developers List
	Subject:	Snapshot 1999-08-12 available

	Hi all,

	I've just finished uploading snapshot 1999-08-12 to the usual place:

	ftp://sourceware.cygnus.com/pub/pthreads-win32

	The announcement is at:

	http://sourceware.cygnus.com/pthread-win32/announcement.html

	Patches and changes from Peter Slacik, Lorin Hochstein, and John
	Bossom have been applied.

	John, the behaviour of pthread_exit() is to raise an exception as
	you suggested which is caught by _pthread_threadStart(). However, if
	the thread was created implicitly pthread_exit just does what it
	used to do, ie. cleanup and end the thread itself. Pthread_exit
	calls pthread_self() which (for those not familiar with John's
	implementation) will create a POSIX thread handle for any thread
	that does not yet have one, ie. was not created by pthread_create(),
	eg. any WIN32 thread, primary thread, etc. This allows those threads
	to be managed by the pthreads routines. Any such POSIX thread handle
	is tagged as "implicit".

	Cheers.
	Ross

	+----------------------+---+
	| Ross Johnson         |   | E-Mail: rpj@ise.canberra.edu.au
	| Info Sciences and Eng|___|
	| University of Canberra   | FAX:    +61 6 2015227
	| PO Box 1                 |
	| Belconnen  ACT    2616   | WWW:
http://willow.canberra.edu.au/~rpj/
	| AUSTRALIA                |
	+--------------------------+