Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21467 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41069 invoked by uid 1010); 10 Jan 2006 22:00:42 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 41054 invoked from network); 10 Jan 2006 22:00:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jan 2006 22:00:42 -0000 X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:34783] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 16/FA-27796-98E24C34 for ; Tue, 10 Jan 2006 17:00:42 -0500 Received: from [192.168.1.3] (dslb-084-063-011-214.pools.arcor-ip.net [84.63.11.214]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 14FD635C1DD; Tue, 10 Jan 2006 23:00:39 +0100 (CET) Date: Tue, 10 Jan 2006 23:00:58 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1049060218.20060110230058@marcus-boerger.de> To: Antony Dovgal Cc: php-dev In-Reply-To: <43C42D85.6060605@zend.com> References: <43C3B9E0.9010502@zend.com> <10410208601.20060110224128@marcus-boerger.de> <43C42D85.6060605@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Exception::fillException() proposal From: helly@php.net (Marcus Boerger) 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? >> 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. Best regards, Marcus