From:	sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject:	RE: ITIMER Implimentation???
4 Dec 1996 02:10:35 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<01BBE1D8.1AA950B0.cygnus.gnu-win32@bbs.prospect.com.ru>
Original-To:	"'Jeremy Allison'" <jra AT cygnus DOT com>
Original-Cc:	"'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com>
Encoding:	24 TEXT
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Jeremy Allison wrote:
>Timers are not implemented yet in cygwin32 (Not even in
>the mythical beta17 :-). The reason is that asynchronous
>signals are not available in NT/95 (for reasons see the VMS
>source code or any other of Dave Cutlers work, ie. it's a
>religious thing :-).

Hopefully, You are not right :-) Win32 API is huge, and contain all 
neccessary functions. And asyncronous timer events too. You may use 
SetTimer(NULL,...). It seems to me, _every_ unix system call may be 
emulated with Win32 API functions! BTW, what about to implement vfork() 
using threads mechanism and fork() with copy-on-write semantic using memory 
mapped files?-)

Furthermore, ALL unix signals can be implemented with Win32 API! Even under 
Windows95. For exampe, SIGCLD signal (death of child process) can be 
emulated with Win32 debug functions, etc...

Once more - Win32 API is huge and rich! And nobody knows this API fully :-)



Sergey Okhapkin
Moscow, Russia

-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -