Re: [PHP-DEV] Re: RFC: Traits for PHP

Hi, I came across one piece of information on aliasing that may not be obvious at first and therefore should probably be explicitly stated in the RFC and in the manual when this makes it into the core. Quoting : "Note that because

[PHP-DEV] Re: RFC: Traits for PHP

[EMAIL PROTECTED] wrote: Hi, during last six months I've studied a language construct called Traits. It is a construct to allow fine-grained code reuse and in my opinon this would be a nice feature for PHP, which I did like to propose here. The following RFC deals with the questions what Traits

Re: [PHP-DEV] Re: RFC: Traits for PHP

Hello Stefan, the biggest issue here is that renaming is still possible. So meanwhile I think that the best approach would be to only allow a method to be inherited as private. So instead of hiding a method completely you get it as a private one. Thus if it collides with an interface you get an

[PHP-DEV] Re: RFC: Traits for PHP

Hi, I've updated the RFC on several sections to reflect the discussion on this list. The following parts have been changed or added: - introduced explicit description of abstract methods to be used as requirements specification for traits (useful to access state) - moved part about inter