Re: Traits for PHP ... Why can't every Class be a Trait?
| From: | D. Dante Lorenso | Date: | Thu, 21 Feb 2008 23:32:25 +0000 |
| Subject: | Re: Traits for PHP ... Why can't every Class be a Trait? | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-35713@lists.php.net to get a copy of this message | ||
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?
-- Dante