On 2017-05-18 03:17, Wollenhaupt, Christof wrote:
I could have swore somebody told me DotNet was MULTIPLE inheritance,
where
you could have multiple parents...which I thought was really great &
cool!
Multiple inheritance of interfaces, but only one actual parent class...
class Class : Parent, Interface1, Interface2, Interface3 { }
I'd argue that there is a good reason not to support multiple
inheritance
as that easily leads to violations of the Single Responsibility
Principle.
--
Christof
Ah...but tell me, can you call to the parent's parent class, like VFP's
class::JumpMoreThanOneLevelUp?
You make a good point of the Single Responsibility Principle, though.
Less confusing and more consistent.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/ff14cea4de6e30c1436395c3ab6b4...@mbsoftwaresolutions.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
