Comments on: How I PHP: multiple inheritance

By: Jon

Jon — Mon, 05 Jul 2010 12:26:01 +0000

There is always an obscure occasion when these kinds of patterns become necessary (e.g. working with Magento where user contributed plug-ins clash due to lack of multiple inheritance). The pattern may not be pretty but it’s ridiculous to dismiss it outright. I never understand people’s fear of programming power.

By: alexbrina

alexbrina — Mon, 28 Sep 2009 18:15:58 +0000

This discussion is good to promote things like that Horizontal Reuse with its Traits and Grafts. I too need a way to share states and behaviors that goes beyond Inheritance and Composition.

By: alexbrina

alexbrina — Mon, 28 Sep 2009 18:07:24 +0000

http://wiki.php.net/rfc/horizontalreuse

By: Artur Ejsmont

Artur Ejsmont — Mon, 28 Sep 2009 08:52:52 +0000

Im sorry but it looks bad to me as well.

PHP projects that use code like that above are notoriously over complicated and debugging or changing anyghing becomaes a real nightmare.

Wrapper itself without __call is a good thing though

I would also discourage from trying to make PHP a language that its not. For example the fact that you can use reflection to mess with an object does not mean you should be doing it. Its an option for cases where its the only way like code analyzers or unit tests frameworks etc.

By: Noel Darlow

Noel Darlow — Sun, 27 Sep 2009 19:28:08 +0000

PS: sorry I didn’t make myself clear, My comments don’t refer to you yoda, or Giorgio.

By: Noel Darlow

Noel Darlow — Sun, 27 Sep 2009 19:24:51 +0000

When I read comments such as above I sometimes wonder if the internet should just be switched off.

Decorating objects is a common problem (I think that’s what’s at the root of this). Wrappers are one solution. “Mixins” (I like to call that method injection http://aperiplus.sourceforge.net/method-injection.php) are another.

I think it’s fair to point out that you should first try to find a single home for related behaviours. There is a danger that you could end up spreading bits of logic around in several classes when they ought to be encapsulated in one unit. Mixed in shouldn’t mean mixed up. At the same time, I think there are situations where you might want to assemble a single (apparent) interface from many parts.

By: Les

Les — Sun, 27 Sep 2009 15:44:21 +0000

There is numerous reasons as to why we don’t have multiple inheritance, and we should not try to implement it, so why do you do it?

This leaves a terrible, vile impression on those who a) are learning about programming for the first time and don’t know any better, and b) those who don’t care about using bad practices.

Everything you have described in this post is bad; I am sure you want to be innovative (we all do) but this isn’t the end result, unfortunately.

Please give yourself a slap… before someone else does

By: Giorgio Sironi

Giorgio Sironi — Sun, 27 Sep 2009 09:50:28 +0000

I think there are more basic techniques to achieve this, like using interfaces for multiple inheritance and then delegation to helper classes.

By: yoda

yoda — Sun, 27 Sep 2009 08:44:02 +0000

This is just a bounch of bad pattern designs which should not be used at all.