Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:5165
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <656F04F343FC25409463829A15B5FDDC3F9605@netwake-nt.netwake.de>
To: internals@lists.php.net
Date: Mon, 3 Nov 2003 10:06:29 +0100 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Supporting php4 (was: Object Equality)
From: Thomas.Lamy@netwake.de (Thomas Lamy)

Andi Gutmans wrote:
> 
> At 03:42 PM 10/9/2003 +0100, Wez Furlong wrote:
> >Interestingly enough, I brought up this issue just over a year
> >ago.  Even more interesting is that I stumbled across my original
> >post from that time while looking into something else today.
> >
> >http://news.php.net/article.php?group=php.dev&article=88735
> >
> >(patch included)
> >
> >--Wez.
> Hi Wez,
> 
> Your patch breaks BC in 4.3.x. As the problem has been solved 
> in PHP 5, I 
> suggest we don't add the patch and wait for the major version 
> to break BC 
> (very slightly).
> 
> Andi
> 
Hi,
does anyone care that there _will_ be a rather big number of folks
(isps/hosting companies/etc) that will stay with 4.x for some time even if
php5 is out?
For me (being a developer) this is no problem, because I always work with
the latest versions. But hosting comanies have to deal with 4 at least 'till
April 2004, if not June. If they have the manpower (and machines) to run
both (4 and 5), they will do so, but others will switch when they feel 5 is
stable enough. Until then, they will have to support 4.
This is why I'm +1 for a 4.5 release, right before 5 goes out. This should
include fixes that already are in 5, but were not applied to 4 for whatever
reason. I'm sure the above fix is not the only one being held back...

Thomas