Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23623
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <4472DE3E.40204@cschneid.com>
Date: Tue, 23 May 2006 12:04:46 +0200
User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308)
MIME-Version: 1.0
To: internals@lists.php.net
References: <7.0.1.0.2.20060523034511.07f184b0@zend.com> <Pine.LNX.4.62.0605230829440.12710@localhost>
In-Reply-To: <Pine.LNX.4.62.0605230829440.12710@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] ze1 compatibility mode
From: cschneid@cschneid.com (Christian Schneider)

Derick Rethans wrote:
> On Tue, 23 May 2006, Zeev Suraski wrote:
>> I know I'm a late bloomer on this one, but when did we discuss the
>> discontinuation of ze1 compatibility mode within the 5.x branch?  I recall we
>> agreed to remove it for 6.0, but removing such a thing in 5.x seems very
>> counterintuitive and counterproductive.
> 
> As a coincidence I tried to run some of our code with this mode on in 
> 5.1.4... crash within the first few lines on some clone... so I'm not so 
> sure how counterintuitive it is to get rid of it ;-)

Lost of people haven't made the step from PHP4 to PHP5 yet and the 
compatibility mode was one of the tools for this. Removing it is 
certainly a big BC break for people who are relying on it right now. It 
might have crashed with your code but it could have worked with others.

On the other hand we tried to use it here and it didn't really help us.

I think what would really help is a tool or mode where the dangerous 
spots in the code could be more easily located. One thing could be a way 
of annotating a class that produces a notice for $a = $b where $b is an 
instance of this class. This is just brainstorming and maybe not that 
useful after all but I don't think the migration path is easy enough as 
it is.

- Chris