From: "Will Bryant" <will.bryant@ecosm.com>
To: <pthreads-win32@sources.redhat.com>
Subject: Re: How is pthread_self() implemented?
Date: Mon, 01 Sep 2003 04:41:00 -0000 [thread overview]
Message-ID: <07ea01c37043$43e02a70$2b01a8c0@moose> (raw)
In-Reply-To: <3F52CBD0.2070205@ise.canberra.edu.au>
> John Bossom's original design also allows for pre-existing Win32 threads
> to use any POSIX routines, and therefore fully interact with POSIX
> threads, by creating a one-time-only on-the-fly detached POSIX thread
> handle for the Win32 thread.
So it is safe to use all pthreads-win32 functions from threads not created
using the pthreads interface? I have an application where nearly all of the
code only needs to use standard windows threads, but there are a couple of
condition variables that I'd like to be able to use...
next prev parent reply other threads:[~2003-09-01 4:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 17:52 Chris Seaton
2003-09-01 4:33 ` Ross Johnson
2003-09-01 4:41 ` Will Bryant [this message]
2003-09-01 7:22 ` Ross Johnson
2003-09-01 15:49 ` Ross Johnson
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='07ea01c37043$43e02a70$2b01a8c0@moose' \
--to=will.bryant@ecosm.com \
--cc=pthreads-win32@sources.redhat.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).