Re: [patch] Zend/zend_objects_API.c - bug #29980 (segfault while executing __destruct())

From: Date: Fri, 10 Sep 2004 16:14:27 +0000
Subject: Re: [patch] Zend/zend_objects_API.c - bug #29980 (segfault while executing __destruct())
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-12718@lists.php.net to get a copy of this message
On Fri, 10 Sep 2004 16:23:41 +0000 Curt Zirzow <curt@php.net> wrote: > Might want to add me to that list :) A use I can see is if the > object manages a buffer of some sort and the destructor ensures > that it is flushed, a bypass of the destructor would cause the > buffer to get lost. Yup. Because it was a *FATAL* error. http://www.php.net/manual/en/ref.errorfunc.php#e-error -- E_ERROR (integer) - Fatal run-time errors. These indicate errors that can not be recovered from, such as a memory allocation problem. Execution of the script is halted. -- I'm not a person to make this decision, but I think that fatal error should really halt execution as the documentation says. -- Wbr, Antony Dovgal aka tony2001 tony2001@phpclub.net || antony@dovgal.com

« previous php.internals (#12718) next »