Re: cvs: php4 /ext/standard file.c

I think that in the last couple of letters we've gone what's reasonable to expect in the real world, and it became an academic discussion. We should: (a) Start using full_write (we can use my_write() off the shelf, I think). (b) Catch this signal, and display a PHP error in case it happens, if we're inside PHP's scope. (c) Optionally, invoke the original signal handler if we're hit by a signal while outside of the PHP scope. If under some circumstances that won't work, tough luck. We can give this option up completely too, as I haven't yet seen any other modules that pay any attention to this signal. Zeev At 18:45 23/12/2000, Sascha Schumann wrote:

    Is there any specific advantage over simply ignoring the
    signal and moving the error handling code into xy_write()?

Well yes, assuming other modules pay attention to this signal...

    Then we are running into other problems, as we don't know
    whether other modules use signal() or sigaction() to set
    their handler.  A signal handler set using signal() is not
    necessarily available through the modern sigaction()
    interface and using signal() to set our own handler won't
    properly interoperate with handlers which were set using
    sigaction().

    - Sascha

-- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-cvs-unsubscribe@lists.php.net For additional commands, e-mail: php-cvs-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net

-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/