Help with pseudo multi inheritance - page 5

New comment
 
Amir Yacoby:

Well, we can debate if dulplicating and maintaining dozens or hundreds of classes and maintain those two sets of duplicate is not a consequence in order to use the observer pattern, but we have better things to do (:



"Consequence" implies defect in code functionality. Inconvenience is the term you're looking for.  

 
nicholishen:


"Consequence" implies defect in code functionality. Inconvenience is the term you're looking for.  

There are defects also, as I said.
In my case, all the classes can be an observer or subject. What you suggest is not supplying this.
Moreover, if I write a new class which is composed of other classes, I need to choose for each class what is the type I will place.
This is not practical, call it whatever name you like.

But, I agree to disagree on this. 
 
Amir Yacoby:
There are defects also, as I said.
In my case, all the classes can be an observer or subject. What you suggest is not supplying this.
Moreover, if I write a new class which is composed of other classes, I need to choose for each class what is the type I will place.
This is not practical, call it whatever name you like.

But, I agree to disagree on this. 
Your statement directly contradicts itself. You still have yet to point out an actual functional defect only inconvenience.
12345
New comment