From: colin@bird.fu.is.saga-u.ac.jp (Colin Peters) Subject: RE: ITIMER Implementation??? 4 Dec 1996 02:18:54 -0800 Sender: daemon@cygnus.com Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <01BBE207.6FE752A0.cygnus.gnu-win32@gbird0.fu.is.saga-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Original-To: "'Jeremy Allison'" Original-Cc: "'GNU-Win32'" Original-Sender: owner-gnu-win32@cygnus.com Jeremy Allison[SMTP:jra@cygnus.com] wrote: >the problem is that UNIX code expects that synchronous I/O >will be interrupted when a signal occurs. Don't tell me it's >bad, that's just the way UNIX code is written, and that's the >way people using Cygwin32 will want it to work :-). Cygwin32 >is not currently MT-safe (that's another bunch of code :-). > >This is not possible on NT currently without me re-writing >all blocking I/O in Cygwin32 to use asynchronous I/O under >the covers and waiting on the handle and a separate event >which the signal thread sets as 'signalled'. This is a lot >of work, hence my statement. It's even worse than that. Asynchronous I/O is not supported under Windows 95. If you want it to work right under 95 (and I for one really do want it to work under 95) and under NT you are definitely in for some long nights ahead. On the other hand, I just want to be able to compile code that runs under 95, not necessarily use the Cygnus library, so I have less problems with this. But I think I'm in the minority there. Colin. -- Colin Peters - colin@bird.fu.is.saga-u.ac.jp -- Saga University Dept. of Information Science -- Fundamentals of Information Science -- http://www.fu.is.saga-u.ac.jp/~colin/home.html - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".