Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:19032 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75335 invoked by uid 1010); 16 Sep 2005 08:05:25 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 75320 invoked from network); 16 Sep 2005 08:05:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Sep 2005 08:05:25 -0000 X-Host-Fingerprint: 194.73.73.210 c2bthomr02.btconnect.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from ([194.73.73.210:4837] helo=c2bthomr02.btconnect.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 2D/32-43379-5CC7A234 for ; Fri, 16 Sep 2005 04:05:25 -0400 Received: from [10.0.0.9] (host81-138-11-136.in-addr.btopenworld.com [81.138.11.136]) by c2bthomr02.btconnect.com (MOS 3.5.9-GR) with ESMTP id CFL73929; Fri, 16 Sep 2005 09:03:37 +0100 (BST) Message-ID: <432A7C68.2000404@lsces.co.uk> Date: Fri, 16 Sep 2005 09:03:52 +0100 Organization: L.S.Caine Electronic Services User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 X-Accept-Language: en, en-us MIME-Version: 1.0 To: pierre.php@gmail.com, internals@lists.php.net References: <7C.1C.41173.4D828234@pb1.pair.com> <63.BA.41173.BB6E8234@pb1.pair.com> <4328EFC1.3030500@lerdorf.com> <38.3D.41173.B58F8234@pb1.pair.com> <4328F9DC.40302@lerdorf.com> <4329550B.90303@lerdorf.com> <9D.D0.41173.FC069234@pb1.pair.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Reference handling change and PHP 4.4.0 From: lester@lsces.co.uk (Lester Caine) Pierre Joye wrote: > All the points I tried to explain in the last 2 months or so were > about that and only that. Every oppinions have been raised. > Short versions: Stop pollitic :) Pierre I think *ONE* problem here was that those of us who have moved on from PHP4 were probably not taking any notice of the discussion relating to that, so WHEN people started complaining that our PHP5 based apps designed to still work with PHP4 were now failing in PHP4 we were not aware of the problem. Greater care SHOULD have been taken in ensuring that ISP's and other 'third party users' were informed that there WOULD be a problem so that they would not just roll out an update. ISP's are not moving to PHP5 BECAUSE code needs fixing and PHP4.4 introduced exactly the sort of problems that is preventing PHP5 being the current PHP base? Perhaps now *IS* the time to drop PHP4 compatibility from my own code :) -- Lester Caine ----------------------------- L.S.Caine Electronic Services