I would need to look into this in more detail but I am not sure sigaction is supported. In any case, these APIs on Windows tend to be more for POSIX compliance and not the "Windows way" so I am not sure there'd be a lot of value in supporting it. In any case, you should probably still take a look but keep this in mind when you're looking at MSDN :)
Andi > -----Original Message----- > From: Pierre Joye [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 24, 2008 12:27 AM > To: Stas Malyshev > Cc: Antony Dovgal; Scott MacVicar; Lucas Nealan; internals@lists.php.net; Andi > Gutmans > Subject: Re: [PHP-DEV] [RFC] Zend Signal Handling > > On Wed, Jul 23, 2008 at 7:54 PM, Stanislav Malyshev <[EMAIL PROTECTED]> wrote: > > Hi! > > > >> Do we really need this option? > >> Is someone going to disable it and why? > > > > I see only reason to disable it if one has some weird system where sigaction > > is either absent or doesn't work as it should. Not that I know of any, but > > Unix variants are full of surprises. > > I'd keep it enabled by default, unless we are on OS that doesn't have > > sigaction (e.g. Windows or some extremely weird Unix) or in ZTS, of course. > > Windows has signal (and SigAction) support. Obviously (sigh) not using > the same API but it is possible to achieve the same behaviors using > the windows API. For example, there is already exception for special > cases like SIGALRM, windows API also uses a timer (CreateWaitableTimer > & co). Once the code is in cvs, I can give it a try to port > zend_signal to windows (not before alpha1 but before alpha2 :) > > Cheers, > -- > Pierre > > http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
