Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58670
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain nebm.ist.utl.pt from 193.136.128.22 cause and error)
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: "PHP internals" <internals@lists.php.net>, "Alan Knowles"
 <alan@akbkhome.com>
References: <4F563667.7080006@akbkhome.com>
Date: Tue, 06 Mar 2012 17:22:00 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Organization: =?utf-8?Q?N=C3=BAcleo_de_Eng=2E_Biom=C3=A9di?=
 =?utf-8?Q?ca_do_I=2ES=2ET=2E?=
Message-ID: <op.warbqyfjidpuyk@slws007.slhq.int>
In-Reply-To: <4F563667.7080006@akbkhome.com>
User-Agent: Opera Mail/11.61 (Win32)
Subject: Re: [PHP-DEV] consider reverting E_ALL with E_STRICT
From: glopes@nebm.ist.utl.pt ("Gustavo Lopes")

On Tue, 06 Mar 2012 17:08:07 +0100, Alan Knowles <alan@akbkhome.com> wrote:

> [...]
> 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...

Whatever the merits, this change was discussed and approved unanimously  
with 58 votes in favor (see https://wiki.php.net/todo/php54/vote ).
There would have to be a very compelling reason to revert this change,  
especially in a minor version.

Moreover, since you upgraded PHP 5.4, you can also change the global  
php.ini to exclude E_STRICT. If your applications change the error  
reporting level, then, if they are sane, they do it in a centralized  
place, which would also be easy to change.

Plus, it seems odd that you're running with display_errors in production.  
The "users see the errors and report them" seems even odder. What a waste  
of their time. Why don't you just log them? You can also automatically  
send e-mails when these errors occur (e.g. with an error handler -- from  
which, btw, you can exclude E_STRICT errors -- or with syslog).

-- 
Gustavo Lopes