Revision as of 16:35, 26 August 2024 edit Qwerfjkl (talk \| contribs) Extended confirmed users, Page movers, Rollbackers 216,529 edits m Added 1 {{Bare URL inline}} tag(s) using a script. For other recently-tagged pages with bare URLs, see Category:Articles with bare URLs for citations from August 2024 ← Previous edit		Revision as of 02:29, 9 March 2025 edit undo 73.136.253.43 (talk) →Basics Tag: Reverted 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