Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23364
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender;
	b=uKV/sUDKs2Fm1K3cFQSKVXlppB1hkWPsrfcxGe6AT37azbVXCBXbEYs627tMBpDGNKTEC0Rj7tMVSbvWZnaDiXE3c3b+d+ISCk9lHgZHy5oT5OS/J3EQZ3D6BrC7ZVTbMh5zp6HH/HAb2lgbCTAE6tKm/nXXNFfxob3ZrmYMUrA=
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 (Apple Message framework v750)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <2D48AB6B-8E19-4274-8E0C-AFEC7BA1702B@prohost.org>
Cc: Steph Fox <steph@zend.com>,
	Marcus Boerger <helly@php.net>,
	Pierre-Alain Joye <pajoye@php.net>,
	internals@lists.php.net
Content-Transfer-Encoding: 7bit
Date: Mon, 15 May 2006 09:14:48 -0400
To: Greg Beaver <cellog@php.net>
Sender: Ilia Alshanetsky <iliaal@gmail.com>
Subject: Re: [PHP-DEV] E_ALL changes in 5.2/6.0
From: ilia@prohost.org (Ilia Alshanetsky)

My opinion is that if we intend to make something stop working (give  
fatal error) in future releases we need to provide some form of  
notice be it E_STRICT or E_NOTICE to our users now, so they can  
anticipate the change. As far as inclusion of E_STRICT into E_ALL, I  
think this is a good idea, but is probably premature for the 5.2  
release.


On 15-May-06, at 6:51 AM, Greg Beaver 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.
>
> Greg
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

Ilia Alshanetsky
Advanced Internet Designs Inc.
ilia@prohost.org