Timeline for Is there any "real" reason multiple inheritance is hated?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 15, 2013 at 14:59 | comment | added | Ordiel | hahaha I'm totally agree with you @Mr.Mindor that's exactly what I'm saying in my answer, the only way that comes to my mind to get near to that aproach is prototype orientated programming, but I'm not saying it's impossible, and that's exactly the reason why I said that that many asumptions must be made during compilation time, and some extra "data"/especifications must be written by teh programmer (nevertheless it is more coding, which was the original problem) | |
| Nov 14, 2013 at 23:03 | comment | added | Mr.Mindor | At what point could a compiler ever assume that variables of the same name from different parent classes are safe to combine? What guarantee do you have that caninus.diet and pet.diet actually serve the same purpose? What would you do with function/methods with the same name? | |
| Nov 14, 2013 at 17:10 | review | First posts | |||
| Nov 14, 2013 at 19:39 | |||||
| Nov 14, 2013 at 17:05 | history | edited | Ordiel | CC BY-SA 3.0 | added 2 characters in body |
| Nov 14, 2013 at 16:52 | history | answered | Ordiel | CC BY-SA 3.0 |