Timeline for "Super" vs "protected method" for running common code
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 18, 2011 at 22:31 | comment | added | Aaronaught | @JoJo: This is still a problem that could be solved by composition. Or perhaps it's simply a badly-designed method. Without far more detailed specifics, it's hard to know how to resolve the design flaw, but it is a design flaw. | |
| May 18, 2011 at 7:04 | comment | added | JoJo | My Kid inherits from Parent because Kid reacts the same as Parent except for one method: someMethod. If Kid had inherited from Grandparent, it would have to copy and paste all but one method from Parent. | |
| May 18, 2011 at 7:01 | vote | accept | JoJo | ||
| May 17, 2011 at 23:34 | comment | added | Gratzy | One of the best answers I have ever read. | |
| May 17, 2011 at 22:56 | history | edited | Aaronaught | CC BY-SA 3.0 | added 244 characters in body; added 222 characters in body |
| May 17, 2011 at 22:54 | comment | added | Aaronaught | @Rein - thanks, I was fishing around in this junkyard I call a memory and couldn't locate the formal name. That's what I was looking for. | |
| May 17, 2011 at 22:50 | comment | added | Rein Henrichs | +1 esp. for "There's no reason to try to fake inheritance when the best possible result is still inferior to simpler alternatives." although would perhaps benefit from mention of LSP | |
| May 17, 2011 at 22:32 | history | answered | Aaronaught | CC BY-SA 3.0 |