Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:35624 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42506 invoked by uid 1010); 19 Feb 2008 22:58:14 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 42491 invoked from network); 19 Feb 2008 22:58:14 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Feb 2008 22:58:14 -0000 Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 212.25.124.162 mail.zend.com Windows 2000 SP4, XP SP1 Received: from [212.25.124.162] ([212.25.124.162:65306] helo=mx1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C1/4C-55225-40F5BB74 for ; Tue, 19 Feb 2008 17:58:13 -0500 Received: from us-ex1.zend.com ([192.168.16.5]) by mx1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 20 Feb 2008 00:58:17 +0200 Received: from [192.168.16.90] ([192.168.16.90]) by us-ex1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 19 Feb 2008 14:58:14 -0800 Message-ID: <47BB5EFE.4080704@zend.com> Date: Tue, 19 Feb 2008 14:58:06 -0800 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 CC: php@stefan-marr.de, internals@lists.php.net References: <001c01c87264$3c01b4e0$b4051ea0$@de> <1203461114.24580.45.camel@localhost> In-Reply-To: <1203461114.24580.45.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 19 Feb 2008 22:58:14.0339 (UTC) FILETIME=[E85F4130:01C8734A] Subject: Re: [PHP-DEV] RFC: Traits for PHP From: stas@zend.com (Stanislav Malyshev) > most important issue to me how to handle interface implementations in > cases where methods from the interface implementing trait are renamed in > the trait consumer class. Renaming poses problem not only with interfaces. Imagine trait having these methods: function add($key, $value) { ... } function delete($key) { ... } function replace($key, $value) { $this->delete($key); $this->add($key, $value); } What happens if add() is renamed or replaced with function from other trait/interface or dropped? -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com