From: andyp AT parallax DOT co DOT uk (Andy Piper) Subject: Re: Thread created for select call! 3 Aug 1998 08:09:43 -0700 Message-ID: <3.0.3.32.19980803154756.00f7ed98.cygnus.cygwin32.developers@exchange.parallax.co.uk> References: <19980803104326 DOT I23956 AT cygnus DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Christopher Faylor , cygwin32-developers AT cygnus DOT com [oops , sorry - XEmacs keybindings in eudora] At 10:43 03/08/98 -0400, Christopher Faylor wrote: >I've rewritten select from scratch recently, so all of those mallocs/frees >are gone. Now there are new ones, but hopefully there are fewer. Presumably the new version includes sergey's /dev/windows implementation? >It still uses thread destruction as a method for determining when a handle >has become "signalled", but it would be easy to change this behavior. I >wrote select with that possibility in mind, in fact. > >This version stands a chance of being in the next public net release. If >there is a great hue and cry, I'll change it to use events as signallers >and try to keep the thread around if possible. The bookkeeping for doing >this kind of thing gets hairy when you have to think about using select >from multiple threads, however. I'm not convinced about the need for this anyhow. select() is usually used as an alternative to muti-threading. andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp AT parallax DOT co DOT uk web: www.parallax.co.uk/~andyp