Revision as of 11:37, 26 June 2023 edit Mahifoo (talk \| contribs) 1 edit Lessened the "inheritance is always bad" mentality to better match the source books. ← Previous edit		Revision as of 12:27, 9 July 2023 edit undo Explicit (talk \| contribs) Autopatrolled, Administrators 370,513 edits m Removing link(s) undefined (XFDcloser) Next edit →
Line 14: ==Basics== An implementation of composition over inheritance typically begins with the creation of various [[Interface (computing)#In object-oriented languages\|interfaces]] representing the behaviors that the system must exhibit. Interfaces can facilitate [[Polymorphism (computer science)\|polymorphic]] behavior. Classes implementing the identified interfaces are built and added to [[business ___domain]] classes as needed. Thus, system behaviors are realized without inheritance. In fact, business ___domain classes may all be base classes without any inheritance at all. Alternative implementation of system behaviors is accomplished by providing another class that implements the desired behavior interface. A class that contains a reference to an interface can support implementations of the interface—a choice that can be delayed until [[Runtime (program lifecycle phase)\|runtime]].

Composition over inheritance: Difference between revisions