Difference between revisions of "Composition over Inheritance"
Jump to navigation
Jump to search
| 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, [[CodeAesthetics]] mentioned that in one video<ref>{{:Video/Prefer Composition Over Inheritance - What Does It Mean?}}</ref>. | For example, [[CodeAesthetics]] mentioned that in one video<ref>{{:Video/Prefer Composition Over Inheritance - What Does It Mean?}}</ref>. Moreover, [[Web Dev Simplified]] also has a video<ref>{{:Video/Composition Vs Inheritance - Why You Should Stop Using Inheritance}}</ref> on this subject. | ||
<noinclude> | <noinclude> | ||
{{PagePostfix | {{PagePostfix | ||
Latest revision as of 01:56, 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, CodeAesthetics mentioned that in one video[1]. Moreover, Web Dev Simplified also has a video[2] on this subject.
References
- ↑ Prefer Composition Over Inheritance - What Does It Mean?. local page: CodeAesthetic. Dec 22, 2022.
- ↑ Cook, Kyle (Jan 5, 2020). Composition Vs Inheritance - Why You Should Stop Using Inheritance. local page: Web Dev Simplified.
Related Pages