Difference between revisions of "Composition over Inheritance"
Jump to navigation
Jump to search
(Created page with "An important design pattern is that inheritance as a programming mechanism can cause more code maintenance troubles for the long run. <noinclude> {{PagePostfix |category_csd=Composition,Inheritance }} </noinclude>") |
|||
Line 1: | Line 1: | ||
An important design pattern is that inheritance as a programming mechanism can cause more code maintenance troubles for the long run. | An important design pattern is that inheritance as a programming mechanism can cause more code maintenance troubles for the long run. | ||
For example, [[Code Aesthetics]] mentioned that in one video<ref>{{:Video/Prefer Composition Over Inheritance - What Does It Mean?}}</ref>. | |||
<noinclude> | <noinclude> | ||
{{PagePostfix | {{PagePostfix |
Revision as of 01:47, 28 December 2022
An important design pattern is that inheritance as a programming mechanism can cause more code maintenance troubles for the long run.
For example, Code Aesthetics mentioned that in one video[1].
References
- ↑ Prefer Composition Over Inheritance - What Does It Mean?. local page: CodeAesthetic. Dec 22, 2022.
Related Pages