Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:12512
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Tue, 31 Aug 2004 21:03:58 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1833935670.20040831210358@marcus-boerger.de>
To: Davey <davey@php.net>
CC: internals@lists.php.net
In-Reply-To: <20040831064149.20909.qmail@pb1.pair.com>
References: <20040831064149.20909.qmail@pb1.pair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] set_exception_handler behaviour change...
From: helly@php.net (Marcus Boerger)

Hello Davey,

Tuesday, August 31, 2004, 8:41:45 AM, you wrote:

> Dear all,

> I would like to request that set_exception_handler's behaviour be 
> changed. IMHO it should not die after handling an exception.


An exception means that the current execution block cannot be
continued and incase that block is not a try block then the stack
is wound up and the next block is skipped until a try block with
a matching catch block is found. The 'cannot' means 'cannot' dot.
If you want to continue from some exceptional behavior than what
you want is some kind of error callback or interrupt. And if one
of those fits then exception are the absolute wrong way. So you
should redesign your software and please never use exceptions for
control flow or parameter passing and never make it a standard
in any way to use exceptions - they are exceptions.

marcus