Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36099 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78558 invoked from network); 11 Mar 2008 13:57:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Mar 2008 13:57:01 -0000 Authentication-Results: pb1.pair.com header.from=m@digitalsandwich.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=m@digitalsandwich.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain digitalsandwich.com from 72.14.220.158 cause and error) X-PHP-List-Original-Sender: m@digitalsandwich.com X-Host-Fingerprint: 72.14.220.158 fg-out-1718.google.com Received: from [72.14.220.158] ([72.14.220.158:36796] helo=fg-out-1718.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 89/42-21537-BAF86D74 for ; Tue, 11 Mar 2008 08:57:00 -0500 Received: by fg-out-1718.google.com with SMTP id 22so1985939fge.23 for ; Tue, 11 Mar 2008 06:56:56 -0700 (PDT) Received: by 10.86.4.2 with SMTP id 2mr8326531fgd.9.1205243816235; Tue, 11 Mar 2008 06:56:56 -0700 (PDT) Received: by 10.86.97.10 with HTTP; Tue, 11 Mar 2008 06:56:56 -0700 (PDT) Message-ID: <8d7b8c130803110656x6ff96ad6q74cbd902e4adeebf@mail.gmail.com> Date: Tue, 11 Mar 2008 06:56:56 -0700 To: "Stanislav Malyshev" Cc: "=?ISO-8859-1?Q?Johannes_Schl=FCter?=" , "PHP Internals List" In-Reply-To: <47D5E32E.4070301@zend.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_21137_9219031.1205243816216" References: <1204823427.30934.9.camel@goldfinger.johannes.nop> <8d7b8c130803092152l6014902cs7b599cec0775015a@mail.gmail.com> <47D56696.7010100@zend.com> <8d7b8c130803101817q129b37ccxdaa069225a0ed0e2@mail.gmail.com> <47D5E32E.4070301@zend.com> Subject: Re: [PHP-DEV] 5.3 Release Planning From: m@digitalsandwich.com ("Mike Lively") ------=_Part_21137_9219031.1205243816216 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Mon, Mar 10, 2008 at 6:41 PM, Stanislav Malyshev wrote: > I must be misunderstanding the patch then - doesn't it change behavior > of the engine so that parent:: doesn't mean "parent of __CLASS__" > anymore? If so, could you explain again what it does? Of course parent:: still means parent. The change in behavior from the current patch is just that once you call parent::someMethod you will still have access to overridden methods in child classes which with the current patch is not possible. Again, it just provides complete polymorphism for statics. parent:: is very simple thing - it means "use the name of the parent > class here". I do not thing changing it is a good idea. I am of the opinion that parent:: simply means call the parent function which doesn't change with the patch. I understand that you do not think it is a good, but I and many other people that have expressed their opinion on list regarding this matter disagree with you. You seem to be very focused on the parent:: issue without looking at the whole picture. Like I said before, I think all of the arguments have been hashed out. I would just like a yes or no decision that preferably reflects the desire of the user base. It would be fantastic if some more decision makers had some time to give their input. > -- > Stanislav Malyshev, Zend Software Architect > stas@zend.com http://www.zend.com/ > (408)253-8829 MSN: stas@zend.com > ------=_Part_21137_9219031.1205243816216--