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 Date: Fri, 19 Nov 1999 13:49:46 -0500 From: Chris Faylor To: DJ Delorie Cc: cygwin@sourceware.cygnus.com Subject: Re: Cygwin select + sockets from DLL Message-ID: <19991119134946.B17821@cygnus.com> Mail-Followup-To: DJ Delorie , cygwin@sourceware.cygnus.com References: <19991119132849.24917.rocketmail@web111.yahoomail.com> <19991119112141.A17177@cygnus.com> <199911191624.LAA31377@envy.delorie.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@cygnus.com http://www.cygnus.com/ -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com