Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: pthread_t and strict standards compliance MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Thu, 25 Apr 2002 10:09:34 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3P0BBT25625 > -----Original Message----- > From: René Møller Fonseca [mailto:fonseca AT mip DOT sdu DOT dk] > Sent: Thursday, April 25, 2002 8:06 AM > To: cygwin AT cygwin DOT com > Subject: Re: pthread_t and strict standards compliance > > > 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. Right. Well any change will _have_ to occur on a cygwin major API boundary - ie from 1.3 to 1.5. That doesn't seem to be in the works yet... If you are interested in contributing a patch, I'll happily review it. Rob -- 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/