Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21466
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <43C42D85.6060605@zend.com>
Date: Wed, 11 Jan 2006 00:56:21 +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>
In-Reply-To: <10410208601.20060110224128@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 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.

> 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?

-- 
Wbr, 
Antony Dovgal