Timeline for "Prefer composition over inheritance" - Is the only reason to defend against signature changes?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 24, 2017 at 13:46 | comment | added | lbenini | Yes, "Composition over inheritance" doesn't mean you don't have interfaces, if you look at the Player object you can see that fit nicely in a hierachy, but at the (excuse the brutalilty) code is not coming from inheritance, but from the composition with some class that does the work | |
| May 24, 2017 at 13:41 | comment | added | Utku | So this section gives a Composition example, right? I am asking because it is not obvious in the article. | |
| May 24, 2017 at 13:41 | review | First posts | |||
| Jun 23, 2017 at 13:30 | |||||
| May 24, 2017 at 13:28 | history | answered | lbenini | CC BY-SA 3.0 |