Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18826 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46904 invoked by uid 1010); 13 Sep 2005 12:58:16 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 46889 invoked from network); 13 Sep 2005 12:58:16 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Sep 2005 12:58:16 -0000 X-Host-Fingerprint: 64.233.184.195 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.195:54950] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id D9/24-58045-7ECC6234 for ; Tue, 13 Sep 2005 08:58:15 -0400 Received: by wproxy.gmail.com with SMTP id 36so2417736wra for ; Tue, 13 Sep 2005 05:58:13 -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=PHdtDaCuMr49DKBih7PyCPjRC6eY2MGlB0/dIxgpNmM2SYjp70N3zUwvqy9gx23FR9++ucNDWuXwURHNgQJR4Luj2ad0YBlJB2bgFz+/1xFFrkdbcLN01V6pJMw34PY6KOqt4I30rlccCuzj1VTZiMc9y5yVdJotoyQcJqiuCfc= Received: by 10.54.39.8 with SMTP id m8mr451790wrm; Tue, 13 Sep 2005 05:58:13 -0700 (PDT) Received: by 10.54.154.16 with HTTP; Tue, 13 Sep 2005 05:58:13 -0700 (PDT) Message-ID: Date: Tue, 13 Sep 2005 14:58:13 +0200 Reply-To: pierre.php@gmail.com To: Rasmus Lerdorf Cc: internals In-Reply-To: <4326CAC3.3080708@lerdorf.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <432534E4.9020602@lerdorf.com> <4326CAC3.3080708@lerdorf.com> Subject: Re: [PHP-DEV] ref fix revisited From: pierre.php@gmail.com (Pierre Joye) On 9/13/05, Rasmus Lerdorf wrote: > Just got back from Sri Lanka and am catching up on email. But in > general I don't agree with your statement that things that are quiet in > 5.0.4 must be quiet in 5.0.5. Quietly corrupting memory doesn't really > work. Sometimes we need to break things slightly to fix things. =20 I agree about the fix, not about the fatal error in 5.0.5. See my answer in my post. > My message was more about if there was a better way to fix it. I looked = at > the code and couldn't tell if it was somehow possible to catch this on > the write instead of on the call. It sounds like that isn't possible. > The second approach to try to regain some backwards compatibility is to > make some of our internal functions aware of the fact that they are > being passed a ref to a temp var and if so pretend it wasn't passed by > reference. As it is too late now anyway, regain BC makes little sense. Unless we restore it all related BC breaks and fix the internal temp vars management (which is equal to a rewrite of this part). From a user point of view, it will only end to the same confusion as in arguments order, or other little annoyances ;) Regards, --Pierre