Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21468
Return-Path: <antony@zend.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 44510 invoked by uid 1010); 10 Jan 2006 22:14:25 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 44495 invoked from network); 10 Jan 2006 22:14:25 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 10 Jan 2006 22:14:25 -0000
X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4)
Received: from ([80.74.107.235:7213] helo=mail.zend.com)
	by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP
	id 4A/4B-27796-FB134C34 for <internals@lists.php.net>; Tue, 10 Jan 2006 17:14:24 -0500
Received: (qmail 24130 invoked from network); 10 Jan 2006 22:14:19 -0000
Received: from internal.zend.office (HELO ?127.0.0.1?) (10.1.1.1)
	by internal.zend.office with SMTP; 10 Jan 2006 22:14:19 -0000
Message-ID: <43C431BA.7070004@zend.com>
Date: Wed, 11 Jan 2006 01:14:18 +0300
User-Agent: Thunderbird 1.5 (X11/20051025)
MIME-Version: 1.0
To: Marcus Boerger <helly@php.net>
CC: php-dev <internals@lists.php.net>
References: <43C3B9E0.9010502@zend.com> <10410208601.20060110224128@marcus-boerger.de> <43C42D85.6060605@zend.com> <1049060218.20060110230058@marcus-boerger.de>
In-Reply-To: <1049060218.20060110230058@marcus-boerger.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Exception::fillException() proposal
From: antony@zend.com (Antony Dovgal)

On 11.01.2006 01:00, Marcus Boerger wrote:
> Hello Antony,
> 
> Tuesday, January 10, 2006, 10:56:21 PM, you wrote:
> 
>> On 11.01.2006 00:41, Marcus Boerger wrote:
>>> Hello Antony,
>>> 
>>>   in general modifying exception data is vey dangerous because first it
>>> leads to confusion on the usage part and second it might lead to sever
>>> problems in the engine facilities that deal with them. That this in a
>>> few cases worked does not mean it works in all cases it mybe be used.
> 
>> Actually, the code doesn't modify any data there, but copies it instead.
>> That is: create new object, copy data from the old one, update few properties.
> 
> And you are sure there is no way this can be executed during shutdown
> sequence?

Except for __destruct() I don't see any other ways for it to be executed during shutdown.
And we know that exceptions work fine in __destruct(). 

>>> To prevent us from adding all the stuff Java invented to deal more
>>> gracefull with exceptions starting with the ability to handle more than
>>> one exception at a time i would like to stay with the KISS approach and
>>> have them as easy as possible.
> 
>> I realize that it's relatively easy to implement this in PHP, but in the same time I don't
>> see in what way adding this function violates the KISS approach. 
>> Could you plz elaborate?
> 
> 
> You are turining Exceptions into Normalities.

Huh?

-- 
Wbr, 
Antony Dovgal