Personally I think that traits is a lot safer than mixing classes.There will
be a lot of things that will need to be considered in order to make it
logical for developers to use.
Quote from the RFC:
"Any method or property that already exists in the class or parent/extended
class cannot be changed
Jonathan Bond-Caron wrote:
> http://wiki.php.net/rfc/mixin
It seems to me that class_mixin() is a bad idea for the core; it's more
of a runkit type functionality than traits. After all, we don't allow
dynamic inheritance, or dynamic interfaces...
--
PHP Internals - PHP Runtime Development Maili
