Re: Reference handling change and PHP 4.4.0
| From: | Leigh Makewell | Date: | Wed, 14 Sep 2005 01:56:43 +0000 |
| Subject: | Re: Reference handling change and PHP 4.4.0 | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-18858@lists.php.net to get a copy of this message | ||
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, --PierreWell 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