Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:18800
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <5.1.0.14.2.20050912173631.07038640@localhost>
Date: Mon, 12 Sep 2005 17:38:56 +0300
To: pierre.php@gmail.com
Cc: internals@lists.php.net
In-Reply-To: <fe05d15405091115543d47fdd8@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] 5.0.5, BC break, fatal error
From: zeev@zend.com (Zeev Suraski)
References: <fe05d15405091115543d47fdd8@mail.gmail.com>

At 01:54 12/09/2005, Pierre Joye wrote:
>Hello,
>
>Without arguing again about the """fix""" for the memory corruption
>discovered earlier this summer and without anyone able to reproduce
>with a medium size script, _why_ in the world one applies this fix to
>the 5.0 branche?
>
>5.0.5 was supposed to be a _security_ fix release only. I do know many
>people who will upgrade and they do have tousands of lines of codes
>wrote by many people. Do you really think the answers given in the
>various bug reports (http://bugs.php.net/bug.php?id=34468) is good?
>
>And please, do not tell me to come with a patch to fix this problem,
>the fix should have not been applied to 5.0.5, period.
>
>Any chance to roll it again without the fix? The fix is not listed in
>the NEWS neither in the Changelog.
>
>I know that the chance to get that fixed is null, but I would like to
>hear some valid explanations besides the common arrogant answers.

Pierre,

I don't think you're going to get a very good answer here.  It boils down 
to what you already know - it's a bug which results in corruption, and 
that's the only way to fix it.  The common decision was that it's more 
important to fix this bug than to maintain compatibility, and this even 
resulted in a new PHP 'family' (4.4).  It's one of those cases where 
there's no good solution, only a choice of bad solutions.

Zeev