Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:12718
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Fri, 10 Sep 2004 20:14:27 +0400
To: internals@lists.php.net
Message-ID: <20040910201427.64e02fd3.tony2001@phpclub.net>
In-Reply-To: <20040910162341.GK58353@bagend.shire>
References: <20040910095725.257bcb8e.tony2001@phpclub.net>
	<20040910162341.GK58353@bagend.shire>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [patch] Zend/zend_objects_API.c - bug #29980
 (segfault while executing __destruct())
From: tony2001@phpclub.net (Antony Dovgal)

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