|
![](/i/fill.gif) |
On 8/13/2012 7:53, Warp wrote:
> If diamond inheritance is the problem, then forbid diamond inheritance.
It turns out that having everything descend from Object (and other tricks
like that) turn out to be more useful than multiple inheritance.
> And it's not like diamond inheritance is forbidden with interfaces (AFAIK,
> although I haven't checked this.)
It doesn't matter there, because the problem with diamond inheritance is
differing implementations and member variables, not the actual methods.
Eiffel did a nice job, but even there they never (AFAIK) actually
implemented the spec.
> But you should be liking C#. It doesn't leak memory and if it crashes, it
> tells you where and why. Probably.
Yep. Unless you explicitly use an unsafe construct.
--
Darren New, San Diego CA, USA (PST)
"Oh no! We're out of code juice!"
"Don't panic. There's beans and filters
in the cabinet."
Post a reply to this message
|
![](/i/fill.gif) |