Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35714
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain stefan-marr.de from 82.96.83.42 cause and error)
Message-ID: <47BE0CC4.1090202@stefan-marr.de>
Date: Fri, 22 Feb 2008 00:44:04 +0100
Reply-To: php@stefan-marr.de
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "D. Dante Lorenso" <dante@lorenso.com>
Cc: Internals Mailing List <internals@lists.php.net>
References: <001c01c87264$3c01b4e0$b4051ea0$@de> <698DE66518E7CA45812BD18E807866CE014A8D9D@us-ex1.zend.net> <47BE0664.8060304@stefan-marr.de> <47BE0A09.6060702@lorenso.com>
In-Reply-To: <47BE0A09.6060702@lorenso.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: Traits for PHP ... Why can't every Class be a Trait?
From: php@stefan-marr.de (Stefan Marr)

Hi,

D. Dante Lorenso schrieb:
> All,
> 
> I can imagine a case where you would want to box common functionality 
> into a trait and be able to use that trait as a class also.  Will we end 
> up with a lot of classes like this?:
> 
> class SomeClass {
>   use SomeTrait;
> }
> 
> What's wrong with making all 'Class'es be 'Trait's and the only thing 
> which makes a Trait a Trait is when you use it as such?
> 
> class MyClass {
>   trait SomeClass;
> }
> 
> In other words, why mustn't a trait be instantiable?  Why can't every 
> Class be a Trait?

Well, the trait concept is not a silver bullet for all problems out there.

What is wrong with inheritance or delegation for reusing complex 
behavior? Traits are for finer grained reuse in my eyes.
The usage I've seen so far suggests typical traits are about 1 to 5 
methods, but the average method count on a trait would be 1.88 or 
something like this (just a rule of thumb. from what I personally have 
looked at).

Kind Regards
Stefan