From: Ross Johnson <rpj@ise.canberra.edu.au>
To: Pthreads Developers List <pthreads-win32@sourceware.cygnus.com>
Subject: Snapshot 1999-08-12 available
Date: Wed, 11 Aug 1999 20:49:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.05.9908121318070.6369-100000@swan.canberra.edu.au> (raw)
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 |
+--------------------------+
next reply other threads:[~1999-08-11 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-11 20:49 Ross Johnson [this message]
1999-09-02 7:15 Medina, Aurelio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.05.9908121318070.6369-100000@swan.canberra.edu.au \
--to=rpj@ise.canberra.edu.au \
--cc=pthreads-win32@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).