X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-Authority-Analysis: v=1.0 c=1 a=g+wkuQswljfnsCw2cQPIHQ==:17 a=w_pzkKWiAAAA:8 a=sLXqwGz61tep1sGeSWAA:9 a=NM-zqUfUpQqvr9dmpXYRuJG7ejEA:4 a=M3PvEdNFSBYA:10 From: mike_cygwin AT comcast DOT net (Mike_Cygwin) To: Subject: RE: Asynchronous i/o Date: Wed, 14 Nov 2007 16:59:31 +0000 Message-Id: <111420071659.12754.473B297300006935000031D2221555588402079909970CA10A050703@comcast.net> X-Mailer: AT&T Message Center Version 1 (Oct 30 2007) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > Should be fairly straightforward to implement, as windows I/O functions > support asynchronous operations (called "overlapped" in msdn technology). You > shouldn't need to modify anything except the cygwin dll sources to add the > functions. > > See > http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin for > some guidelines on how to build the cygwin dll from source. When adding new > functions to the DLL, you also need to list them in the "cygwin.din" file - > that defines which functions get exported and which don't. > > OK...learning. ;-[) My reason for asking these questions is because some of the digging I did suggested there were other things not yet implemented that would make it near impossible to do this (something about pthreads). What I am hearing now is that this not the case (anymore). I will look at the links you provided. Thanks, Mike -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/