Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23399 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79047 invoked by uid 1010); 15 May 2006 18:35:00 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 79032 invoked from network); 15 May 2006 18:35:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 May 2006 18:35:00 -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:55708] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 56/EA-19568-4D9C8644 for ; Mon, 15 May 2006 14:35:00 -0400 Received: from baumbart.mbo (dslb-084-063-060-049.pools.arcor-ip.net [84.63.60.49]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 5976F35C1E8; Mon, 15 May 2006 20:34:57 +0200 (CEST) Date: Mon, 15 May 2006 20:35:00 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <934611092.20060515203500@marcus-boerger.de> To: Ilia Alshanetsky Cc: Derick Rethans , Greg Beaver , Steph Fox , Pierre-Alain Joye , In-Reply-To: <22A06B02-0F5B-4A77-956C-DA2B5F26D4C7@prohost.org> References: <138663365.20060514205903@marcus-boerger.de> <038d01c676f8$ab9b3380$6602a8c0@foxbox> <44685D24.2000801@php.net> <2D48AB6B-8E19-4274-8E0C-AFEC7BA1702B@prohost.org> <22A06B02-0F5B-4A77-956C-DA2B5F26D4C7@prohost.org> 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 Ilia, Monday, May 15, 2006, 3:23:18 PM, you wrote: > I suggest that we add E_STRICT now, but not include E_STRICT into > E_ALL, We added E_STRICT in what 5.0 or or 5.1? Guess i checked it: marcus@zaphod /usr/src/php-cvs $ cvs annotate Zend/zend_errors.h|grep E_STRICT Annotations for Zend/zend_errors.h *************** 1.15 (andi 18-Nov-03): #define E_STRICT (1<<11L) 1.22 (dmitry 16-Mar-06): #define E_ALL (E_ERROR | E_WARNING | E_PARSE | E_N marcus@zaphod /usr/src/php-cvs $ cvs log Zend/zend_errors.h|grep php_5_0_0b php_5_0_0b4: 1.17 php_5_0_0b4RC1: 1.17 php_5_0_0b3: 1.16 php_5_0_0b3RC2: 1.16 php_5_0_0b3RC1: 1.16 php_5_0_0b2: 1.14 php_5_0_0b2RC1: 1.14 php_5_0_0b1: 1.14 marcus@zaphod /usr/src/php-cvs $ > so people who are not using E_STRICT error reporting level > don't have their applications start spewing strict messages. > We cannot force people to change their code, all we can reasonably do > is provide notification mechanism, for those who do. Yes and that is E_STRICT. And if we continue the way we do now we will have not only unicode problems when people upgrade to 6... > On 15-May-06, at 9:16 AM, Derick Rethans wrote: >> On Mon, 15 May 2006, Ilia Alshanetsky wrote: >> >>> My opinion is that if we intend to make something stop working >>> (give fatal >>> error) in future releases we need to provide some form of notice >>> be it >>> E_STRICT or E_NOTICE to our users now, so they can anticipate the >>> change. As >>> far as inclusion of E_STRICT into E_ALL, I think this is a good >>> idea, but is >>> probably premature for the 5.2 release. >> >> Then when do you suggest we add it (before 6.0)? >> >> regards, >> Derick >> > Ilia Alshanetsky > Advanced Internet Designs Inc. > ilia@prohost.org Best regards, Marcus