Comments on: Traits for a new template engine

By: lawrence

lawrence — Fri, 30 Oct 2009 00:11:51 +0000

Fabian, seems like you could recreate some aspects of AOP using traits. But certain styles of action hooking would still need to be done with factory methods or closures.

By: Fabian

Fabian — Thu, 29 Oct 2009 21:49:33 +0000

I am not really fond of mixins. Hooking code is unpredictable. And you can achieve code reuse by other means. Like injecting a service with IoC.
I would never have thought somebody says: inheritance is for code reuse.
if you do want to code crossfunctional code only once, I would go into the direction of AOP. (Not sure if traits mimic that)

By: lawrence

lawrence — Mon, 26 Oct 2009 21:36:01 +0000

davide, ‘traits’ would not become part of the inheritance tree of the class that you include them in. So, for instance, if you have an IDE that shows you all the methods in your class, you would avoid the explosion of methods that Michele Simionato wrote of. Really, if you want to know the worst anti-pattern of Ruby Mixins, read Michele Simionato’s article. I linked to it above.

By: davide

davide — Mon, 26 Oct 2009 19:04:05 +0000

I think traits would be something like module mixins in ruby, if you’re familiar…

By: What would the ideal template system be for Symfony?

What would the ideal template system be for Symfony? — Sun, 25 Oct 2009 05:46:21 +0000

[...] About reusability, he says he is looking forward to having ‘traits’ in PHP. See my last post for more about that. [...]

By: Closer To The Ideal » Blog Archive » Traits will bring something like mixins to PHP

Sat, 24 Oct 2009 18:02:57 +0000

[...] I’ve a new post up over at Symfony Nerds. It is all about how ‘traits’ will bring something like Mixins to PHP. [...]