This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Reason for cover functions in pthread.cc
- To: Cygwin Developers <cygwin-developers at sourceware dot cygnus dot com>
- Subject: Re: Reason for cover functions in pthread.cc
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Mon, 8 May 2000 11:50:52 -0400
- References: <000001bfb89f$94694120$6401a8c0@jupiter>
- Reply-To: cygwin-developers at sourceware dot cygnus dot com
On Sun, May 07, 2000 at 10:43:31PM -0500, Paul K. Fisher wrote:
>Is there a reason to keep the cover functions in pthread.cc? These simply
>call "__" prefixed versions in thread.cc, where the real implementation is
>provided.
>
>For example:
>int
>pthread_attr_init (pthread_attr_t * attr)
>{
> return __pthread_attr_init (attr);
>}
I don't know of any reason for this practice. It has always mystified me.
Do things __pthread_attr_init exist in the spec? If so, the place to handle
this is in cygwin.din not in a wrapper function.
cgf