Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50366
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain stefan-marr.de from 85.88.12.247 cause and error)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <AANLkTik5bUFavCswVU8arECNXcsebMPyMYb0t31NX02G@mail.gmail.com>
Date: Thu, 18 Nov 2010 19:00:51 +0100
Cc: PHP Development <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <89F665AA-1F23-41D1-B1D8-F9C078637A2E@stefan-marr.de>
References: <AANLkTik5bUFavCswVU8arECNXcsebMPyMYb0t31NX02G@mail.gmail.com>
To: Patrick ALLAERT <patrickallaert@php.net>
Subject: Re: [PHP-DEV] Trait behavior when providing a new name while no conflict exists
From: php@stefan-marr.de (Stefan Marr)

Hi Patrick:

On 18 Nov 2010, at 16:01, Patrick ALLAERT wrote:

> Hi,
>=20
> Is this intended not being able to give a new name to a method even in
> case of no conflict?
> In the following example, I try to provide the name "sayIt"
> additionally to "saySomething" from trait "Hello":
>=20
> <?php
> trait Hello {
>   public function saySomething() {
>     echo 'Hello';
>   }
> }
>=20
> class MyHello{
>   use Hello {
>         Hello::saySomething as sayIt;
>   }
> }
> ?>

Thanks for catching this, it is a bug.
It works without the Hello:: part and it should also work with the =
Hello::.

Fixed with the following commit: =
http://svn.php.net/viewvc?view=3Drevision&revision=3D305512

Best regards
Stefan


--=20
Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
http://soft.vub.ac.be/~smarr
Phone: +32 2 629 2974
Fax:   +32 2 629 3525