Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23356 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 23524 invoked by uid 1010); 15 May 2006 07:01:33 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 23508 invoked from network); 15 May 2006 07:01:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 May 2006 07:01:33 -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:53878] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 4F/49-19568-B4728644 for ; Mon, 15 May 2006 03:01:32 -0400 Received: from baumbart.mbo (dslb-084-063-032-006.pools.arcor-ip.net [84.63.32.6]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 086EF35C1E8; Mon, 15 May 2006 09:01:28 +0200 (CEST) Date: Mon, 15 May 2006 09:01:28 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <207855155.20060515090128@marcus-boerger.de> To: Lukas Smith Cc: Derick Rethans , internals@lists.php.net In-Reply-To: <4468231D.6000604@php.net> References: <138663365.20060514205903@marcus-boerger.de> <4468231D.6000604@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] E_ALL changes in 5.2/6.0 From: helly@php.net (Marcus Boerger) Hello Lukas, Monday, May 15, 2006, 8:43:41 AM, you wrote: > Derick Rethans wrote: >> On Sun, 14 May 2006, Marcus Boerger wrote: >> >>> That said i am about to not remove E_STRICT from E_ALL and MFH the php >>> 6.0 to item just now. >>> See: http://oss.backendmedia.com/PhP60 (add E_STRICT to E_ALL DONE (dmitry)) >>> >>> Since this is for the benefit of the users to prevent issues with >>> changes in behavior from my opinion it is best to do this behavior >>> change as early as possible, which is in my opinion 5.2 anyway. >>> >>> That said i'll let it in and if there is no valid argument against, i >>> will put it into the NEWS file and the newly started README.UPDATE_5_2. >> >> Yup, I agree on this. > The key point is that with reading the upgrading guide people will know > howto get the old behavior. I do not quite agree that this change is > necessary, but I guess the "ALL" in "E_ALL" implies it includes > everything, so its logical on that level. > regards, > Lukas > PS: Obviously this will be quite painful for PEAR, but I guess that is > partially the point here: create some pains to nudge people towards > writing PHP5 only code. Or maybe its just about covering our asses > against users who complain about us removing deprecated functionality > after a few minor releases. Sorry i have to say that but PEAR is no argument here as still after years of PHP 5 there is no PHP 5 compatible PEAR. Yet we are discussing a PHP 5 version here. Best regards, Marcus