public inbox for
 help / color / mirror / Atom feed
From: Ross Johnson <>
To: pthreads-win32 <>
Subject: Re: snap-2004-11-03 breakage
Date: Wed, 03 Nov 2004 15:38:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <0c1d01c4c1b6$210857a0$>

Gisle Vanem wrote:

> "Ross Johnson" wrote:
>> I definitely don't want to break applications unnecessarily and 
>> particularly applications that have been ported to several different 
>> POSIX systems, but on the other hand POSIX thread IDs are not 
>> required to be scalar. See the rationale from the definition of 
>> pthread_equal() in the Single Unix Specification version 3, which says:
> Great, but when was pthread_equal() introduced? I'd like to support
> old versions of pthread-win32 too.
pthread_equal() has been in pthreads-win32 since 1998. pthread_kill() 
with the sigzero functionality is a lot newer - introduced in 

> BTW. I cannot find a compile-time VERSION define to check against.
> If there where, I could #ifdef around this problem.

I should have done that for this snapshot. Don't be surprised to see a 
new snapshot in a day or two just to include that.

> BTW2. I'm, getting 2 copies of every reply from you. I would prefer 
> replies
> to go to the list only. Could you please make the mailing-list program 
> add a "Reply-to" header?
I have no control over the mailing list, but I can save you from getting 
two copies from me.

> --gv

  reply	other threads:[~2004-11-03 15:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 13:18 Gisle Vanem
2004-11-03 14:28 ` Robert Kindred
2004-11-03 16:18   ` Ross Johnson
2004-11-03 16:30     ` Peter Slacik
2004-11-04 18:06     ` Robert Kindred
2004-11-03 14:33 ` Ross Johnson
     [not found] ` <>
2004-11-03 15:02   ` Gisle Vanem
2004-11-03 15:38     ` Ross Johnson [this message]
2004-11-03 15:32 ` Alexander Terekhov
2004-11-03 16:19   ` Ross Johnson
2004-11-03 16:32     ` Alexander Terekhov
2004-11-03 16:15 Bossom, John

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).