Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23506
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <446ABE45.2040501@lerdorf.com>
Date: Tue, 16 May 2006 23:10:13 -0700
User-Agent: Thunderbird 3.0a1 (Macintosh/20060414)
MIME-Version: 1.0
To: Ilia Alshanetsky <ilia@prohost.org>
CC: PHP Internals List <internals@lists.php.net>
References: <6C67DAD9-B812-415A-BFD6-A4E963371551@prohost.org>
In-Reply-To: <6C67DAD9-B812-415A-BFD6-A4E963371551@prohost.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Flamewar Summary
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Ilia Alshanetsky wrote:
> 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

I don't like E_ALL & ~E_NOTICE suddenly starting to throw E_STRICT in a 
minor version upgrade.  So I am -1 on that one as well.  We agreed to do 
this in PHP 6 a while ago.  What has changed to move that to 5.x now?

> Addition of support for dynamic statics ala: class foo {} foo::$bar = 1;

I don't really see why we need strictness here.  If people want to 
redefine their statics on the fly, why get in their way?  Of course, I 
also don't see why you would want to change the class definition on the 
fly like this.  And would it change already instantiated objects of that 
class as well?  So I am not against it assuming the semantics are sane. 
  +0 I guess.

-Rasmus