Timeline for Code re-use in C++, via multiple inheritance or composition? Or...?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 6, 2018 at 16:37 | comment | added | Zelta | This won't compile as is. You have to implement all abstract methods in Actual_object and Another_object and than delegate to the correct implementation. And this is the main drawback of this method... | |
| Aug 18, 2014 at 8:34 | comment | added | Leo | I like this. So long as the naming is consistent I don’t think the deviation from orthodox OOP is going to be a huge issue. Public inheritance fulfils contracts, protected inheritance implements. CRTP is better if everything can be resolved at compile-time, but as you say it means you can’t create a heterogenous container of subclass instances. | |
| Aug 15, 2014 at 20:20 | history | answered | Emilio Garavaglia | CC BY-SA 3.0 |