Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Date: Fri, 19 Nov 1999 13:49:46 -0500 From: Chris Faylor To: DJ Delorie Cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Cygwin select + sockets from DLL Message-ID: <19991119134946.B17821@cygnus.com> Mail-Followup-To: DJ Delorie , cygwin AT sourceware DOT cygnus DOT com References: <19991119132849 DOT 24917 DOT rocketmail AT web111 DOT yahoomail DOT com> <19991119112141 DOT A17177 AT cygnus DOT com> <199911191624 DOT LAA31377 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199911191624.LAA31377@envy.delorie.com>; from dj@delorie.com on Fri, Nov 19, 1999 at 11:24:03AM -0500 On Fri, Nov 19, 1999 at 11:24:03AM -0500, DJ Delorie wrote: >>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. > >Will the cygwin_attach_handle_to_fd() function help? Probably. Then we'd be on to the next problem... It's a valid suggestion, though. -- cgf AT cygnus DOT com http://www.cygnus.com/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com