Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23496 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8761 invoked by uid 1010); 16 May 2006 23:50:32 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 8744 invoked from network); 16 May 2006 23:50:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 May 2006 23:50:32 -0000 X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:59967] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id DD/2A-19568-8456A644 for ; Tue, 16 May 2006 19:50:32 -0400 Received: from baumbart.mbo (dslb-084-063-059-004.pools.arcor-ip.net [84.63.59.4]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id CA37535C1DC; Wed, 17 May 2006 01:50:29 +0200 (CEST) Date: Wed, 17 May 2006 01:50:36 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <13310440138.20060517015036@marcus-boerger.de> To: Ilia Alshanetsky Cc: PHP Internals List In-Reply-To: <6C67DAD9-B812-415A-BFD6-A4E963371551@prohost.org> References: <6C67DAD9-B812-415A-BFD6-A4E963371551@prohost.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Flamewar Summary From: helly@php.net (Marcus Boerger) Hello Ilia, Wednesday, May 17, 2006, 1:26:37 AM, you wrote: > Inclusion of E_STRICT and E_RECOVERABLE_ERROR into E_ALL +1 I gave my best on this. But be sure. I'll just ignore any whining on any change that has a E_STRICT in older versions when doing changes in any version after 5.2. Also before you think removing E_STRICT solves everything; Well it doesn't. While doing all the stuff we wanted for 5.2 we also added E_RECOVERABLE_ERROR. This includes stuff that was E_ERROR before hand. And right now we didn't even start to systematically convert all error modes in the extension directory as we started to do in HEAD. That said you most likely have to fix your error_reporting anyway or just don't care at all since you use settings that just work yor you. An argument i heared was that some applications that deal with error_reporting might get into trouble with this. I have a solution to that: we simply revert all the engine changes, or even better simply rebranch 5.1.4 again and do not do any progress other than fixing bugs and focusing on PHP 6.0. > Addition of support for dynamic statics ala: class foo {} foo::$bar = 1; -1 If we go that road i suggest we simply drop support for strict. Fixing the issues we will run into is quite impossible and even if it were it would lead to a slower php. A php that doesn't support strict at all would on the other hand be quite a bit faster. Best regards, Marcus p.s: And no, i wouldn't take it personally if someone reverts all my stuff as long as it is decided by the RM. I would simply whine for the around 50 hours of unpaid work :-)