Newsgroups: php.cvs,php.internals Path: news.php.net Xref: news.php.net php.cvs:48242 php.internals:35086 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19542 invoked by uid 1010); 1 Feb 2008 23:27:17 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 19510 invoked from network); 1 Feb 2008 23:27:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Feb 2008 23:27:16 -0000 Authentication-Results: pb1.pair.com smtp.mail=helly@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=helly@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender) X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 85.214.94.56 aixcept.net Linux 2.6 Received: from [85.214.94.56] ([85.214.94.56:49303] helo=h1149922.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 12/97-04011-2DAA3A74 for ; Fri, 01 Feb 2008 18:27:16 -0500 Received: from MBOERGER-ZRH.corp.google.com (202-168.79-83.cust.bluewin.ch [83.79.168.202]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by h1149922.serverkompetenz.net (Postfix) with ESMTP id F28EC1B364D; Sat, 2 Feb 2008 00:27:10 +0100 (CET) Date: Sat, 2 Feb 2008 00:26:39 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <187241737.20080202002639@marcus-boerger.de> To: Lukas Kahwe Smith CC: "Pierre Joye" , php-cvs@lists.php.net, In-Reply-To: References: <574269741.20080201224537@marcus-boerger.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: [PHP-CVS] [ZEND-ENGINE-CVS] cvs: ZendEngine2(PHP_5_3) / zend_API.c zend_API.h php-src/ext/standard type.c From: helly@php.net (Marcus Boerger) Hello Lukas, only E_ERROR is fatal and reserved for when the engine cannot continue execution. marcus Friday, February 1, 2008, 11:15:08 PM, you wrote: > On 01.02.2008, at 23:05, Pierre Joye wrote: >> 2008/2/1 Marcus Boerger : >>> Crosspost, hopefully silencing this issue for 5.* >>> >>> AND 6 will have an E_WARNING or even an E_ERROR on this. >> >> What are the gains? >> >> What are the real reasons behing strictness? I really get annoying by >> adding fatal errors all around for no technical reasons. A fatal error >> means the engine is getting foo bared and can't do anything sane but >> leaving. > Yes .. I think for PHP we should follow these rules: > 1) No fatal errors that are not fatal for the engine > 2) throw E_STRICT for anything that makes a CS prof commit suicide > PHP is about solving real world problems and not creating problems > that are not there (making on fatal things fatal is creating a non > existant problem). if people want to do the right thing in terms of CS > they enable E_STRICT .. and if they want E_STRICT to be fatal they can > create an error handler that does that for them. > regards, > Lukas Best regards, Marcus