Timeline for Inheritance using non-abstract base class
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Aug 2, 2012 at 11:11 | comment | added | vaughandroid | If you're designing from the ground up and have full control over the design, then I don't think I can come up with such a scenario: in that situation I think your rule is a pretty good one. I'm really saying that inheriting from a non-abstract class is not necessarily a bad thing. | |
| Aug 2, 2012 at 10:54 | comment | added | LCJ | Thanks. The Dog-IDog issue comes due to external issues - like external API. Can you provide a scenario like - I have full control of all my classes - still inheritance can be better (with non-abstract base class). I am checking all possibilities :-) | |
| Aug 2, 2012 at 9:46 | history | answered | vaughandroid | CC BY-SA 3.0 |