Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35653
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender)
Date: Wed, 20 Feb 2008 20:59:51 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1495054633.20080220205951@marcus-boerger.de>
To: "Stefan Marr" <php@stefan-marr.de>
CC: Evert|Rooftop <evert@rooftopsolutions.nl>, 
	"Stanislav Malyshev" <stas@zend.com>, <internals@lists.php.net>
In-Reply-To: <1e12984d0802191359p4f21c3acrdff4b86adfb4bf3@mail.gmail.com>
References: <001c01c87264$3c01b4e0$b4051ea0$@de> <173732199.20080219175837@marcus-boerger.de> <1203452909.24580.9.camel@localhost> <1e12984d0802191323o710c6b8ej3a54af7901cf35f1@mail.gmail.com> <47BB4AC9.9070701@zend.com> <1e12984d0802191346x7c145d7fp14c01ec4e5993779@mail.gmail.com> <47BB4F49.1030904@rooftopsolutions.nl> <1e12984d0802191359p4f21c3acrdff4b86adfb4bf3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Traits for PHP
From: helly@php.net (Marcus Boerger)

Hello Stefan,

  so at th eend of the day users will get renaming and will abuse it.
That said I am wondering if at the beginning we might want to do Traits
without aliasing and dropping. If we feel it gets necessary we probbaly
might want to support a syntax like:
  'trait_method' => false
  'trait_method' => 'new_name'
  'trait_method' => array('new_name', 'trait_method'

I am suggesting this because it is more what people expect to find. And it
is easier to understand imo.

marcus

Tuesday, February 19, 2008, 10:59:20 PM, you wrote:

> Hi Evert,

>> Aliasing doesn't make a lot of sense, as you can always :
>>
>> function newMethod() {
>>   return $this->oldMethod();
>> }

> Don't think so.
> You do use aliasing to handle conflicts and in the case of a conflict
> there is no oldMethod.

> trait A {
>   public function foo() {echo 'foo';}
> }

> trait B {
>   public function foo() {echo 'fooBar';}
> }

> class MyClass {
>   use A;
>   use B {
>     !foo, fooBar => foo
>   }
> }

> The result will be at runtime:

> class MyClass {
>   public function foo() {echo 'foo';}
>   public function foo() {echo 'fooBar';}
> }

> Here you can't do something like this:

> class MyClass {
>   use A;
>   use B;
> }

> since eventually there wont be any method in MyClass.




Best regards,
 Marcus