public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "Gisle Vanem" <giva@bgnett.no>
To: "pthreads-win32" <pthreads-win32@sources.redhat.com>
Subject: Re: snap-2004-11-03 breakage
Date: Wed, 03 Nov 2004 15:02:00 -0000	[thread overview]
Message-ID: <0c1d01c4c1b6$210857a0$0600000a@broadpark.no> (raw)
In-Reply-To: <4188EB13.8000100@ise.canberra.edu.au>

"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.

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

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?

--gv

  parent reply	other threads:[~2004-11-03 15:02 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] ` <4188EB13.8000100@ise.canberra.edu.au>
2004-11-03 15:02   ` Gisle Vanem [this message]
2004-11-03 15:38     ` Ross Johnson
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:
  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='0c1d01c4c1b6$210857a0$0600000a@broadpark.no' \
    --to=giva@bgnett.no \
    --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).