Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Chris Faylor Date: Fri, 19 Nov 1999 11:21:41 -0500 To: Cygnus - Admin Cc: Earnie Boyd , Peter Hudson +44 1892 541 720 , cygwin@sourceware.cygnus.com Subject: Re: Cygwin select + sockets from DLL Message-ID: <19991119112141.A17177@cygnus.com> Mail-Followup-To: Cygnus - Admin , Earnie Boyd , Peter Hudson +44 1892 541 720 , cygwin@sourceware.cygnus.com References: <19991119132849.24917.rocketmail@web111.yahoomail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cygnus@ncohafmuta.com on Fri, Nov 19, 1999 at 08:50:33AM -0500 On Fri, Nov 19, 1999 at 08:50:33AM -0500, Cygnus - Admin wrote: >On Fri, 19 Nov 1999, Earnie Boyd wrote: >>Well, unless the third party software uses cygwin1.dll (which I doubt), >>then based up the quoted comments you can't use the Cygwin select. You >>must use the Windows sockets.h header and function set. > >are you serious? i can't use select() if i'm not gonna use the windows >header files? He's serious and he's correct. cygwin fd's != "fd"'s returned by a winsock socket operation. You can't use raw winsock file handles in cygwin select. Cygwin maintains its own table of file descriptors so you can't mix cygwin functions with non-cygwin file descriptors. -Chris Faylor -Cygwin Engineering Manager -Cygnus Solutions -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com