In article [EMAIL PROTECTED],
Craig Rodrigues [EMAIL PROTECTED] wrote:
pthread_self() returns something of type pthread_t.
This code works under Linux, because pthread_t is mapped to an integer value.
However, on FreeBSD, pthread_t is a pointer to struct pthread, so this
code does not
On Thu, Feb 27, 2003 at 08:40:22AM -0800, John Polstra wrote:
FreeBSD violates POSIX in this respect.
Doh! I just looked at:
http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libpthread/include/pthread.h
and it looks like OpenBSD does the same thing.
Just wondering, is the FreeBSD KSE project
John Polstra [EMAIL PROTECTED] writes:
In article [EMAIL PROTECTED],
Craig Rodrigues [EMAIL PROTECTED] wrote:
pthread_self() returns something of type pthread_t.
This code works under Linux, because pthread_t is mapped to an integer value.
However, on FreeBSD, pthread_t is a pointer
In article [EMAIL PROTECTED],
Mike Barcroft [EMAIL PROTECTED] wrote:
John Polstra [EMAIL PROTECTED] writes:
FreeBSD violates POSIX in this respect. The 1003.1 standard
(section 2.5) requires pthread_t to be an arithmetic type.
It looks like this requirement was removed in POSIX.1-2001.
On Thu, 27 Feb 2003 08:40:22 -0800 (PST), John Polstra [EMAIL PROTECTED] said:
FreeBSD violates POSIX in this respect. The 1003.1 standard
(section 2.5) requires pthread_t to be an arithmetic type. We are
non-compliant in the same way for almost all of the primary
thread-related types:
Not
On Thu, 27 Feb 2003 09:06:41 -0800 (PST), John Polstra [EMAIL PROTECTED] said:
Interesting. I don't have that standard and wasn't aware of the
change.
You do. It's available for free on the Web from opengroup.org. Free
registration is required. Mike may still have some copies of the
John Polstra [EMAIL PROTECTED] writes:
In article [EMAIL PROTECTED],
Mike Barcroft [EMAIL PROTECTED] wrote:
John Polstra [EMAIL PROTECTED] writes:
FreeBSD violates POSIX in this respect. The 1003.1 standard
(section 2.5) requires pthread_t to be an arithmetic type.
It looks like
In article [EMAIL PROTECTED], Mike
Barcroft [EMAIL PROTECTED] wrote:
So it looks like pthread_t must be an arithmetic type, but not the
others.
Great. Thanks for checking!
John
--
John Polstra
John D. Polstra Co., Inc.Seattle, Washington USA
Disappointment
In article [EMAIL PROTECTED],
Garrett Wollman [EMAIL PROTECTED] wrote:
We could define pthread_t as __intptr_t without making significant
changes to the implementation.
Agreed. I think it would be nicer if it were a small integer like
a file descriptor -- i.e., an index into a table
On 27-Feb-2003 Craig Rodrigues wrote:
On Thu, Feb 27, 2003 at 08:40:22AM -0800, John Polstra wrote:
FreeBSD violates POSIX in this respect.
Doh! I just looked at:
http://www.openbsd.org/cgi-bin/cvsweb/src/lib/libpthread/include/pthread.h
and it looks like OpenBSD does the same thing.
Maybe it is possbile to create wrappers for these types in your portable
program
Is pthread_t a simple handle for the memory location of the
pthread_t strucutre?
On Thu, 2003-02-27 at 11:40, John Polstra wrote:
In article [EMAIL PROTECTED],
Craig Rodrigues [EMAIL PROTECTED] wrote:
Craig Rodrigues wrote:
return static_castunsigned long(pthread_self());
pthread_self() returns something of type pthread_t.
This code works under Linux, because pthread_t is mapped to an integer value.
However, on FreeBSD, pthread_t is a pointer to struct pthread, so this
code does not
Hi,
I have a question about OpenSSL 0.9.7.
On the following web page:
http://www.openssl.org/docs/crypto/threads.html
void CRYPTO_set_id_callback(unsigned long (*id_function)(void));
id_function(void) is a function that returns a thread ID.
It is not needed on Windows nor on platforms where
13 matches
Mail list logo
