Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18859 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22746 invoked by uid 1010); 14 Sep 2005 02:36:34 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 22730 invoked from network); 14 Sep 2005 02:36:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Sep 2005 02:36:34 -0000 X-Host-Fingerprint: 204.11.219.139 lerdorf.com Linux 2.4/2.6 Received: from ([204.11.219.139:41063] helo=colo.lerdorf.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 47/7A-41173-1BC87234 for ; Tue, 13 Sep 2005 22:36:33 -0400 Received: from [192.168.2.102] (CPE00131063dcac-CM0011aec551ea.cpe.net.cable.rogers.com [65.49.170.67]) (authenticated bits=0) by colo.lerdorf.com (8.13.4/8.13.4/Debian-4) with ESMTP id j8E2aKSQ003019 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 13 Sep 2005 19:36:22 -0700 Message-ID: <43278CA4.4030701@lerdorf.com> Date: Tue, 13 Sep 2005 22:36:20 -0400 User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Leigh Makewell CC: internals@lists.php.net References: <43276022.6020702@encode.net.au> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Reference handling change and PHP 4.4.0 From: rasmus@lerdorf.com (Rasmus Lerdorf) Leigh Makewell wrote: > Pierre Joye wrote: > >> No, 4.3.x is a dead branche. But the problem is much more easier to >> fix in 4.4.0. Do what you always do in production servers, do not >> display errors/notices, especially as 4.4.0 raises only notices for >> the reference problem. >> >> Regards, >> >> --Pierre > > > Well that is exactly why this is a problem. Making large changes that > break BC in php 5 is fine because there are two versions that are being > maintained, php4, and php5. Security updates are made to both. > > However, breaking BC between 4.3 and 4.4 when 4.3 is a dead branch > causes can cause some problems for system admins. What happens if the > software being used is never updated to 4.4? There are important > security updates that need to be applied, but they can't apply them > because all of their websites will stop working. > > Oh and not displaying the error doesn't make the error go away :p Once again, it is an E_NOTICE in 4.4. And yes, not displaying it makes it go away. Staying with 4.3 because of this is nuts. If you are seeing this notice under 4.4 that means you are most likely getting random memory corruption under 4.3. Move to 4.4 to fix the memory corruption. Go through the notices and fix as many of them as you can, since it indicates a basic problem in the code you are running. If you are not interested in doing that, just turn them off. It will run without corruption. -Rasmus