Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18801 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78083 invoked by uid 1010); 12 Sep 2005 14:50:12 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 78068 invoked from network); 12 Sep 2005 14:50:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Sep 2005 14:50:12 -0000 X-Host-Fingerprint: 64.233.184.205 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.205:29152] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 47/D0-27924-2A595234 for ; Mon, 12 Sep 2005 10:50:11 -0400 Received: by wproxy.gmail.com with SMTP id 36so2233488wra for ; Mon, 12 Sep 2005 07:50:07 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ImX1EgobTX/lHYekCew2MJN9SjHfepZxtQ3/4x6becbfdyQDdu1iyWj+FGqa+Fn/bDBIimzgS0XZDprw4iJfG7mlLgJXevHepH6f1MuX+jKT7rE8SXFAvR0RTN8ArENy8xGMbIwBgzzUhvQyNUE8IQvo0vYUKxwrSc+wLeyzy3A= Received: by 10.54.14.59 with SMTP id 59mr2676027wrn; Mon, 12 Sep 2005 07:50:06 -0700 (PDT) Received: by 10.54.154.16 with HTTP; Mon, 12 Sep 2005 07:50:06 -0700 (PDT) Message-ID: Date: Mon, 12 Sep 2005 16:50:06 +0200 Reply-To: pierre.php@gmail.com To: Zeev Suraski Cc: internals@lists.php.net In-Reply-To: <5.1.0.14.2.20050912173631.07038640@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <5.1.0.14.2.20050912173631.07038640@localhost> Subject: Re: [PHP-DEV] 5.0.5, BC break, fatal error From: pierre.php@gmail.com (Pierre Joye) On 9/12/05, Zeev Suraski 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? ;) The bad solution is to do not communicate about that. Reading the announce of 5.0.5, the only real problem was xml_rpc... If one has asked to apply the fix to 5.0.5, I'm pretty sure nobody will agree to add this fatal error. Regards, --Pierre