Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23400
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Mon, 15 May 2006 20:40:40 +0200
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1408277471.20060515204040@marcus-boerger.de>
To: Greg Beaver <cellog@php.net>
Cc: Steph Fox <steph@zend.com>, Pierre-Alain Joye <pajoye@php.net>,
	<internals@lists.php.net>
In-Reply-To: <44685D24.2000801@php.net>
References: <138663365.20060514205903@marcus-boerger.de> <038d01c676f8$ab9b3380$6602a8c0@foxbox> <44685D24.2000801@php.net>
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 Greg,

Monday, May 15, 2006, 12:51:16 PM, you wrote:

> Steph Fox wrote:
>> Marcus,
>> 
>> FWIW I'm with you (unusually) over E_STRICT. Why would anyone have E_ALL
>> switched on anywhere but a dev box? - and when there is the option to
>> switch on E_ALL  without E_STRICT, it makes it much easier to miss
>> useful information about the direction PHP is going in.
>> 
>> Pierre: the biggest E_STRICT issues I'm aware of are the 'vars don't
>> live here any more' one (which was removed two months ago in PHP_5_1
>> branch) and the 'only variables can be passed by reference' one (which
>> is in PHP 4.4.* anyway).  Beyond those two, it ought to be pretty rare

> Side note: calling functions statically that do not have a static
> modifier causes E_STRICT.  Hello PEAR::isError()

> This is of course going to be a fatal in PHP 6, but it is now the most
> common E_STRICT I see in PHP4-based code.

> I agree that it is appropriate to change something like this in a 5.X.0,
> but it will be a headache for anyone running legacy apps (not just
> PEAR).  Until someone writes some killer apps in PHP5 to replace phpBB
> and company, changes of this nature will simply prevent moving to PHP5
> but that's another story and not the concern of internals (I agree with
> this strongly).  If you all are willing to deal with the fallout (think
> PHP 4.4) then that's that.


Ones again E_ALL is for development. For example to move PEAR code to PHP 5.
It is not for running legacy apps. IF you guys want i'd be ok with adding a
new mode say "E_RUN"...



Best regards,
 Marcus