Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50347
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        b=skHopjBi8TvhPF/TAspexepe3Xcs1tFW22DYyDxGoh4s/QYtoUYe5rOSGLGFgdlnvT
         GL037x53+I3vFGog7aW+2OE4X6ZeBkGx+1PV2cFzbThYjARbx0VWOvgE6Mb/Aq85nGG6
         7O87SZejZwnY3YmXE/U/vtIarJq3DAyd267ss=
MIME-Version: 1.0
Sender: patrick.allaert@gmail.com
Date: Thu, 18 Nov 2010 16:01:56 +0100
Message-ID: <AANLkTik5bUFavCswVU8arECNXcsebMPyMYb0t31NX02G@mail.gmail.com>
To: PHP Development <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Trait behavior when providing a new name while no conflict exists
From: patrickallaert@php.net (Patrick ALLAERT)

Hi,

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":

<?php
trait Hello {
   public function saySomething() {
     echo 'Hello';
   }
}

class MyHello{
   use Hello {
         Hello::saySomething as sayIt;
   }
}
?>

The following error message is shown while running it:

Fatal error: Failed to add aliased trait method (sayIt) to the trait
table. There is probably already a trait method with the same name in
%s on line %d

The error message might be misleading even if it should only be
available in case of conflict.

Regards,

-- 
Patrick Allaert
---
http://code.google.com/p/peclapm/ - Alternative PHP Monitor