Newsgroups: php.cvs,php.internals Path: news.php.net Xref: news.php.net php.cvs:48239 php.internals:35081 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 94063 invoked by uid 1010); 1 Feb 2008 22:16:03 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 94046 invoked from network); 1 Feb 2008 22:16:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Feb 2008 22:16:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 85.10.196.195 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 85.10.196.195 serveforce1.backendmedia.com Linux 2.6 Received: from [85.10.196.195] ([85.10.196.195:52266] helo=serveforce1.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FD/63-04011-02A93A74 for ; Fri, 01 Feb 2008 17:16:02 -0500 Received: from Soitgoes (p57BB505B.dip.t-dialin.net [87.187.80.91]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by serveforce1.backendmedia.com (Postfix) with ESMTP id 62A001224907; Fri, 1 Feb 2008 23:17:10 +0100 (CET) Cc: "Marcus Boerger" , php-cvs@lists.php.net, internals@lists.php.net Message-ID: To: "Pierre Joye" In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Fri, 1 Feb 2008 23:15:08 +0100 References: <574269741.20080201224537@marcus-boerger.de> X-Mailer: Apple Mail (2.915) X-backendmedia-com-MailScanner-Information: Please contact the ISP for more information X-backendmedia-com-MailScanner: Found to be clean X-backendmedia-com-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=0.075, required 6, AWL -0.03, RDNS_DYNAMIC 0.10) X-backendmedia-com-MailScanner-From: mls@pooteeweet.org X-Spam-Status: No 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: mls@pooteeweet.org (Lukas Kahwe Smith) 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