From: Michael Bieber <onsager@gmx.net>
To: pthreads-win32@sourceware.org
Subject: Re: Accessing Windows thread id
Date: Sun, 27 May 2007 09:07:00 -0000 [thread overview]
Message-ID: <893096451.20070527093039@gmx.net> (raw)
In-Reply-To: <46584240.7060108@homemail.com.au>
RJ> I'll add another function to the library to return this nicely - called,
RJ> say, pthread_getw32threadid_np().
Hallo Ross,
I was able to circumvent my particular problem, but the new function
should be helpful for some other cases too.
Thank you,
Micha
p.s. The library did a great job during a Linux->Windows port of 100
kLOC, saving a *lot* of time here. Additionally, it is very helpful in
maintaining a common source tree for both OS variants of our software.
Keep up the good work and thank you again!
prev parent reply other threads:[~2007-05-27 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 14:21 Michael Bieber
2007-05-27 7:30 ` Ross Johnson
2007-05-27 9:07 ` Michael Bieber [this message]
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=893096451.20070527093039@gmx.net \
--to=onsager@gmx.net \
--cc=pthreads-win32@sourceware.org \
/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).