Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49133 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19626 invoked from network); 23 Jul 2010 18:36:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2010 18:36:18 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.173 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.173 smtp173.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.173] ([67.192.241.173:57165] helo=smtp173.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4B/EB-53775-021E94C4 for ; Fri, 23 Jul 2010 14:36:17 -0400 Received: from relay7.relay.dfw.mlsrvr.com (localhost [127.0.0.1]) by relay7.relay.dfw.mlsrvr.com (SMTP Server) with ESMTP id E39C2CE4E3B; Fri, 23 Jul 2010 14:36:11 -0400 (EDT) Received: by relay7.relay.dfw.mlsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 6FCF8CE669F; Fri, 23 Jul 2010 14:36:11 -0400 (EDT) Message-ID: <4C49E11A.1080708@sugarcrm.com> Date: Fri, 23 Jul 2010 11:36:10 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Karoly Negyesi CC: "internals@lists.php.net" References: <730E72B7-B2C3-4FF9-8138-F04659ECDB56@php.net> <4C4950B2.40805@thelounge.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Remove variable function and method calls From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > If you treat ::$ as a single construct in your mind then you will get > classname::$foo() wrong. Of course the rule is that classname::.....() is a > method call but it's less evident by just looking at the code. It's really not that hard. It'd take you 1/100 of the time you are wasting discussing it to learn it, and that's counting only your time. > I have suggested that removing the $foo() construct completely, $foo(), > $bar->$foo(), bar::$foo() all would solve this and although it breaks backwards > compatibility, there is a perfect replacement by using call_user_func() instead. That will not happen. There's tons of downsides and not one single upside to it. > I have implied that PHP does not care about backwards compatibility breaking and > this especially will be true for the next release. This was supported by my > experience working with various PHP versions over many years. This is plain false. PHP does care for BC a lot. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227