Subject: Re: pthread_t and strict standards compliance
From: René Møller Fonseca <[email-masked]>
To: [email-masked]
Date: Thu, 25 Apr 2002 00:05:40 +0200

Hi Heribert,

Of course, you are right. But I'm interested in the most correct 
implementation of the standard(s) and that implies following the very 
word of the standard in question. This policy will generally reduce the 
work required when the standard is revised. Something  that seems not to 
be a problem may turn out to be a big one when the standard is revised 
and things MUST BE kept backwards-compatible.

René

Heribert Dahms wrote:
> Hi René,
> 
> (not having reread SUS) how does a pointer hurt?
> If you are a thread user, and not implementer,
> you should treat it as an opaque type anyway,
> just storing or passing around to next thread function!
> What's the sense of the sum or difference of pthread_t's?
> Wait, you can also compare for equality,
> but that works for pointers...
> 
> Bye, Heribert ([email-masked])
> 
> 
>>-----Original Message-----
>>From:	René Møller Fonseca [SMTP:[email-masked]]
>>Sent:	Wednesday, April 24, 2002 22:40
>>To:	[email-masked]
>>Subject:	pthread_t and strict standards compliance
>>
>>Hi,
>>
>>I was porting my framework to Cygwin and noticed that pthread_t is a 
>>typedef of a void pointer.
>>
>>According to "The Single UNIX Specification, Version 2" and "IEEE Std 
>>1003.1-2001" pthread_t must be defined as an arithmetic type (i.e. 
>>either a floating-point type or an integral type). The pointer type is 
>>NOT an arithmetic type even though some arithmetic operators may be 
>>applied to a pointer.
>>
>>René
>>
>>-- 
>>B.Sc. in Computer Systems Engineering
>>The Maersk Mc-Kinney Moller Institute for Production Technology
>>University of Southern Denmark
>>http://www.mip.sdu.dk/~fonseca
>>
> 
> 

-- 
B.Sc. in Computer Systems Engineering
The Maersk Mc-Kinney Moller Institute for Production Technology
University of Southern Denmark
http://www.mip.sdu.dk/~fonseca

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/