Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Sun, 7 May 2000 21:53:04 -0400 To: Cygwin Developers Subject: Re: Incorrect prototypes for some pthread functions Message-ID: <20000507215304.A12598@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, Cygwin Developers References: <000901bfb88d$f4333780$6401a8c0 AT jupiter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: <000901bfb88d$f4333780$6401a8c0@jupiter>; from pfisher@plexware.com on Sun, May 07, 2000 at 08:37:21PM -0500 On Sun, May 07, 2000 at 08:37:21PM -0500, Paul K. Fisher wrote: >Greetings. Just joined the list, and second time I am posting. Overall I >am looking into pthread support. Now on to the question. > >I have found that some of the prototypes for the pthreads functions appear >to be incorrect. For example, pthread_kill is prototyped as: > >int pthread_kill( pthread_t * thread, int sig ); > >and it seems that it should be: > >int pthread_kill( pthread_t thread, int sig ); > >Of course, this probably still works, but causes a compilation warning. >There are several other cases of where this occurs. Any reason for this. I >am referring to the UNIX 98 spec as a reference. Is there something else to >which this has been implemented? > >If these are really incorrect, I will submit a patch. If the spec says something different, then this is a bug. Feel free to submit a patch for this and to supply any missing prototypes. Please make sure that you use GNU standards with any code that you supply. The thread stuff was formatted abominably before so don't let that be your guide. But you already knew that... cgf