Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:20197 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93448 invoked by uid 1010); 20 Nov 2005 14:56:26 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 93433 invoked from network); 20 Nov 2005 14:56:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Nov 2005 14:56:26 -0000 X-Host-Fingerprint: 195.227.108.51 wfserver02.wf-ppr.de Windows 2000 SP2+, XP SP1 (seldom 98 4.10.2222) Received: from ([195.227.108.51:55134] helo=wfserver02.wf-ppr.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id D2/9D-11378-99E80834 for ; Sun, 20 Nov 2005 09:56:26 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 20 Nov 2005 15:56:20 +0100 Message-ID: <00A2E2156BEE8446A81C8881AE117F192C1BD0@companyweb> Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PHP-DEV] Curlies again [was: Upgrade notes for PHP 5.1 - final draft] Thread-Index: AcXt2WgVP4ouOemdTN+8P3elPuksGAACMgrA To: "Derick Rethans" Cc: "internals" Subject: AW: [PHP-DEV] Curlies again [was: Upgrade notes for PHP 5.1 - final draft] From: mp@webfactory.de ("Matthias Pigulla") Derick, > If you prefer a PHP which causes strange crashses and memory > corruptions, please downgrade to 4.3.11. I am getting tired=20 > about this=20 > bickering about this **FIX** that makes PHP stable. You got me wrong here. I did not want to say anything against the 4.4.0 fix or even blame you for it. But: nobody doubts that there has been a lot of public discussion about it, that people were upset because they felt the language has been changed in a way that caused them a lot of work and because their scripts suddenly broke (and if only a by showing a warning or notice, however). I was only saying that you (i. e. the people who have enough karma to make the final decisions here) should not light-heartedly make such a change - and in this case, with no obvious need for it (apart from cleaning up - I know myself that sometimes this is tempting for developers). As to the possible impact - I did a quick scan of Smarty and phpDocumentor (because I used to have CVS HEAD checkouts of them at hand) and found that both of them would be affected. Please, do not make such a change that late in an RC5 and push it out with PHP5.1. At least give the maintainers of popular PHP based projects some time to pick it up and test it. As with the 4.4.0, this is nothing you cannot fix or workaround or suppress with an appropriate config. But once again the average user out there might once again feel lost out there simply because his hoster did the upgrade. -mp.