Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23539
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Reply-To: <Jared.Williams1@ntlworld.com>
To: "'PHP Internals List'" <internals@lists.php.net>
Date: Wed, 17 May 2006 14:41:37 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <6C67DAD9-B812-415A-BFD6-A4E963371551@prohost.org>
Thread-Index: AcZ5QEnRHNYZNoCXQkOCIu4PhoIknwAdfSog
Message-ID: <20060517133744.VFBO24467.aamtaout02-winn.ispmail.ntl.com@win2ks>
Subject: RE: [PHP-DEV] Flamewar Summary
From: jared.williams1@ntlworld.com ("Jared Williams")
References: <6C67DAD9-B812-415A-BFD6-A4E963371551@prohost.org>


> There are 2 PHP 5.2 changes there has been a lot of back and 
> forth flaming going around and we need to finally come to a 
> decision about.
> 
> The two topics are:
> 
> Inclusion of E_STRICT and E_RECOVERABLE_ERROR into E_ALL 
> Addition of support for dynamic statics ala: class foo {} 
> foo::$bar = 1;

E_RECOVERABLE_ERROR +1

As for E_STRICT, am I right in thinking that some E_STRICT warnings are generated by the parser, and before any PHP code is
executed? So using error_reporting(E_ALL & ~E_STRICT) is never going to prevent some E_STRICT warnings? 
If so -1, as E_STRICT behaves differently compared to the other E_*s, otherwise 0.


foo::$bar = 1;
-1

Jared