Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23946 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77004 invoked by uid 1010); 4 Jun 2006 23:49:53 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 76988 invoked from network); 4 Jun 2006 23:49:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jun 2006 23:49:53 -0000 X-PHP-List-Original-Sender: danielc@analysisandsolutions.com X-Host-Fingerprint: 166.84.1.73 mail2.panix.com Received: from ([166.84.1.73:56887] helo=mail2.panix.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id B7/60-00946-1A173844 for ; Sun, 04 Jun 2006 19:49:53 -0400 Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail2.panix.com (Postfix) with ESMTP id BD8C69D850 for ; Sun, 4 Jun 2006 19:49:48 -0400 (EDT) Received: (from analysis@localhost) by panix5.panix.com (8.11.6p3/8.8.8/PanixN1.1) id k54NnmY29420 for internals@lists.php.net; Sun, 4 Jun 2006 19:49:48 -0400 (EDT) Date: Sun, 4 Jun 2006 19:49:48 -0400 To: PHP Internals List Message-ID: <20060604234948.GA12106@panix.com> References: <649570026.20060531004803@marcus-boerger.de> <447DA723.9090108@zend.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <447DA723.9090108@zend.com> User-Agent: Mutt/1.5.10i Subject: Re: [PHP-DEV] [RFC] E_STRICT From: danielc@analysisandsolutions.com (Daniel Convissor) On Wed, May 31, 2006 at 06:24:35PM +0400, Antony Dovgal wrote: > > So that E_STRICT notices introduced in 6.x will become E_FATALs only in 7.0 > and so on. That's pretty much what I was going to say. To be clear, unlike the commit that was recently reverted, E_STRICT should never be moved into E_ALL. What should change is the type of error the behaviors trigger. So, something from PHP 4 that triggers an E_STRICT in PHP 5 should trigger an E_WARNING (or whatever) in PHP 6. This leaves E_STRICT available for use in PHP 6 to tag deprecated items from PHP 5 that will trigger E_WARNINGS in PHP 7. And on and on... --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409