Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17244 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86224 invoked by uid 1010); 12 Jul 2005 19:19:47 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 86208 invoked from network); 12 Jul 2005 19:19:47 -0000 Received: from unknown (HELO pb1.pair.com) (127.0.0.1) by localhost with SMTP; 12 Jul 2005 19:19:47 -0000 X-Host-Fingerprint: 84.57.8.84 dsl-084-057-008-084.arcor-ip.net Received: from ([84.57.8.84:20911] helo=localhost.localdomain) by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP id 6B/A1-23681-3D714D24 for ; Tue, 12 Jul 2005 15:19:47 -0400 To: internals@lists.php.net Date: Tue, 12 Jul 2005 21:20:26 +0200 Message-ID: <20050712212026.5bd2dbbb.pierre@dotgeek.org> References: <20050712105234.5dhkvvd6ghcsw8sg@marina.horde.org> X-Newsreader: Sylpheed version 2.0.0beta1 (GTK+ 2.4.14; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Posted-By: 84.57.8.84 Subject: Re: [PHP-DEV] php 4.4 BC break From: pierre@dotgeek.org (Pierre-Alain Joye) On Tue, 12 Jul 2005 20:53:16 +0200 (CEST) derick@php.net (Derick Rethans) wrote: > On Tue, 12 Jul 2005, Chuck Hagenbuch wrote: > > > Relax, I'm not debating the decision. Just: > > > > PLEASE can someone put a big fat warning on the php 4.4 > > announcement on www.php.net that it breaks existing code? > > > > I already have people upgrading to it and wondering why they > > get tons of warnings now. We're fixing them as quick as we can, > > but honestly, given that PHP never gave us a notice about them > > before, there are going to be a lot, and a lot in old releases > > too. It'd be helpful if on the php side people were at least > > given a chance not to shoot themselves in the foot. > > They were already shooting them in the foot by using references > wrong... and you did have about a month to test your code (Horde > I presume) with the new PHP 4.4 release candidates. And it's just > a notice... which you should always have off on a production > machine. So I don't think we should put a BIG warning on php.net > because people didn't quite understand how references worked (me > included). The bug #33643 is not what I can call "shooting in my own foot". There were cases were I fully agree to break BC, but this one and its pairs, not. I agree that it's nice to solve this problem, my point here is we fix a Zend bug by removing some facilities in the langage. I only hope that we will allow that again in future versions. --Pierre