Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58666
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain akbkhome.com designates 202.81.246.113 as permitted sender)
Message-ID: <4F563667.7080006@akbkhome.com>
Date: Wed, 07 Mar 2012 00:08:07 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: consider reverting E_ALL with E_STRICT
From: alan@akbkhome.com (Alan Knowles)

I just got caught on a production server with the 5.4 upgrade on debian, 
pretty much everything works fine, except the E_ALL change.

I have to admit I missed the discussion where it was added, and 
searching for E_ALL or E_STRICT on marc is pretty difficult (it removes 
the E_ bit..)

Anyway, this change is a bit of an bomb on the code on the first server 
to get hit with this, While i've never cared for E_STRICT (it's more 
like E_ANAL) - most of the warnings are pointless code tidy up's that 
only have pretty much zero cost/return in fixing.

However, this change really kills code written by third parties, All our 
servers run with E_ALL on (eg. E_NOTICE is printed to end users) and we 
fix instantly any errors that the end users see, as they are frequently 
issues that should have been addressed. These applications are 
intra/extranet apps, not public websites.

However with E_STRICT included we have to run around and find all the 
code, and change it to stuff like this:

error_reporting(E_ALL & E_STRICT ? E_ALL ^ E_STRICT : E_ALL);

Could we please revert that, and if people want an all encompasing error 
mode, call it E_ANAL, like it was supposed to be...

Regards
Alan