Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:12492
Return-Path: <davey@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 20966 invoked by uid 1010); 31 Aug 2004 06:41:49 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 20910 invoked by uid 1007); 31 Aug 2004 06:41:49 -0000
Message-ID: <20040831064149.20909.qmail@pb1.pair.com>
To: internals@lists.php.net
Date: Tue, 31 Aug 2004 02:41:45 -0400
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 MultiZilla/1.6.4.0b
X-Accept-Language: en-us, en
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Posted-By: 4.4.208.222
Subject: set_exception_handler behaviour change...
From: davey@php.net (Davey)

Dear all,

I would like to request that set_exception_handler's behaviour be 
changed. IMHO it should not die after handling an exception.

I feel that most users will expect this behaviour to be synonymous (i.e. 
both should echo "foo"):

try {
    throw someException;
}
catch (someException $e) { }

echo "foo";

and:

throw someExceptionThatIsCaughtBySetExceptionHandler;

echo "foo";

Derick has expressed that all uncaught exceptions should cause an 
E_ERROR, and I agree, however I feel that set_exception_handler means 
that the exception is handled, just by a default function (say, a logger).

There is currently a rather large (and heated) debate on pear-dev about 
how to not get in a mess with PHP5 error handling, and I have proposed 
a nice solution (IMO) which relies on the behaviour I propose.

- Davey