On Mon, 12 Sep 2005, Pierre Joye wrote: > On 9/12/05, Zeev Suraski <[EMAIL PROTECTED]> wrote: > > > 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. > > 4.4.0, correct and I do accept that. but not in 5.0.5. Derick applied > the patch to 5.1 not to 5.0.5. We did agree to apply it there and not > in bug fix releases (and not in security release). Or can you point me > to the common decision? ;)
I didn't even apply it to 5.1, otherwise it would have been a notice there too. Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
