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 Message-Id: <199912080415.WAA13883@mercury.xraylith.wisc.edu> To: John Fortin cc: "cygwin-developers AT sourceware DOT cygnus DOT com" Subject: Re: pthreads status? [was Re: [Fwd: Many changes in latest snapshot]] In-Reply-To: Your message of "Tue, 07 Dec 1999 20:44:48 EST." <384DB810 DOT 57DA8A2B AT ibm DOT net> Date: Tue, 07 Dec 1999 22:15:28 -0600 From: Mumit Khan John Fortin writes: > Mumit, > Here are the various pthread functions defined in cygwin.din. > The 2 major file for pthread implementation are pthread.cc, thread.cc > There are also thread.h and include/pthread.h include files. > > Hope this helps [ ... ] Certainly does! Now I know I shouldn't even try my code for a while ;-) Just searched the archives for both cygwin and cygwin-developers lists, looking for pthread related discussion. Not much at all, so here're my two little questions: 1. Anybody actively working on it? 2. Why not try to reuse code from pthreads-win32 project? License issue raises its ugly head again (isn't the copyright there owned by Cygnus as well?)? > > pthread_key_create NO > pthread_key_delete NO > pthread_setspecific NO > pthread_getspecific NO I can cook these up when I get some time. > pthread_mutex_init ? > pthread_mutex_lock ? > pthread_mutex_unlock ? > pthread_mutex_destroy ? These are quite tricky to get right ... I have to find out if my minimal tests failed because of other bugs, or these are not quite working as expected. I hate debugging threaded code, as much as I hate debugging startup code. The trouble are the various missing types and macros. I'm hoping to get a bit of free time soon, so perhaps I'll take a look. Now if I can only find my pthreads reference ... Regards, Mumit