I was waiting after Rasmus said he wanted to compare to the internal
Signals code they have at Yahoo before asking againd about inclusion.
Gopal is familiar with the Yahoo code as well and we're planning to
get together tomorrow and to review and make sure there aren't any
critial oversights on this implementation. If the timeline allows 5.3
would be great but we may want to wait until Friday to commit.
It makes sense to me to enable by default on systems that have
sigaction and disable on those without. This happens curretly in the
patch if it's enabled and not present. I did check some discussions
from other projects where this has come up and of was found to be
available on almost all systems a number of years ago. I can dig this
up and add to the rfc soon.
-lucas (mobile)
On Jul 23, 2008, at 10:55, "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.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
