Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18938 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 98465 invoked by uid 1010); 14 Sep 2005 22:27:15 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 98450 invoked from network); 14 Sep 2005 22:27:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Sep 2005 22:27:15 -0000 X-Host-Fingerprint: 203.12.160.103 mail7.tpgi.com.au Received: from ([203.12.160.103:46538] helo=mail7.tpgi.com.au) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 2C/26-41173-0C3A8234 for ; Wed, 14 Sep 2005 18:27:13 -0400 Received: from [127.0.0.1] (220-245-213-234-act.tpgi.com.au [220.245.213.234]) by mail7.tpgi.com.au (8.13.4/8.13.4) with ESMTP id j8EMR1PF019522; Thu, 15 Sep 2005 08:27:08 +1000 Message-ID: <4328A3B3.2080800@encode.net.au> Date: Thu, 15 Sep 2005 08:26:59 +1000 Organization: Encode Polymedia User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derick Rethans CC: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-TPG-Antivirus: Passed Subject: Re: [PHP-DEV] Reference handling change and PHP 4.4.0 From: colin@encode.net.au (Colin Tucker) Derick Rethans wrote: >>We found this out the hard way yesterday when our server administrator >>upgraded our production server to PHP 4.4.0 (even though the Debian package >>description said it was a PHP 4.3.x release). We ended up with hundreds of >>errors and many, many vhosts stopped working correctly due to "variable >>references should be returned by reference" problems, both in my code and in >>third-party code, such as PHPBB instances. > > Uhm, they're only notices - they shouldn't show up at the website in > production, now should they? Derick, can you show me where I said that they showed up on the website? >>And now I read that this will not be "fixed" in future PHP4 releases due to >>breaking backwards compatibility? I just don't understand... a change that >>breaks backwards compatibility in a large portion of the existing PHP4 code >>base will not be fixed because it breaks backwards compatibility? It's doing >>my head in, please can someone explain? > > PHP 4 is not going to change the behavior anymore. Sorry, but that doesn't really answer my question. Regards, Colin.