What is the primary competing design pattern for specific inheritance in application architecture?

Question

Sometimes I come across comments about inheritance that are “out of style” in the corporate application architecture, but I did not find a link to an article describing a competing theory. Also, is there a difference in implementation if the application is already built as opposed to starting from scratch? I believe that this may be due to a greater load on the interfaces, but I'm not sure.

Answer 1

I think you are referring to the Design Principle:

"Approve composition over Inheritance."

Answer 2

( ) .

,

 public class B extends A implements I {
    // now I have all the methods from A
 }

public class B implements I {
     private I a;

     // delegate all methods
     public void methodOne(){
          a.methodOne();
     }
}

, :

• ( , , Java)
• ( , , , ).
• ( ). .

Answer 3

, - , , :

Phillips , Flatheads.

, , , , .

- "is-a" vs. "has-a" - , ( ), . , .

, . : " , ", " - ", ? ?

- . , - , ; -)

[ !]

Answer 4

, . : .

: , , , , , . - , , .

Answer 5

Smalltalk Perl. . .

Answer 6

, . 2003 , - . , 2009 !

Answer 7

++, mixins ( : , mixins):

Wikipedia: http://en.wikipedia.org/wiki/Mixin
Dr. Dobbs: http://www.ddj.com/cpp/184404445.

" " (CRTP):

Wikipedia: http://en.wikipedia.org/wiki/Curiously_Recurring_Template_Pattern.

CRTP mixins, .

"" ( ), , mixins . , , , .

, CRTP , ( ) , . , .

... , ++, . mixin .

mixins , . , , . , " " , , "", .