Re: multiple inheritance
- From: Jon Skeet [C# MVP] <skeet@xxxxxxxxx>
- Date: Thu, 6 Apr 2006 18:36:42 +0100
Shawnk <Shawnk@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Do you think this (valiant but flawed) effort is indicative of;
1. Inherent Jitter architecture flaw/weakness
2. Inherent MSIL architecture flaw/weakness
3. Inherent Multilple Inheritance problem with Von Nueman (turing tape)
engines
I think it's the normal problem of trying to make a square peg fit in a
round hole. The framework has its own idioms, and Eiffel wants to
bypass those idioms.
Without *some* idioms/rules, the CLR would be too general to be useful,
IMO. However, no set of idioms/rules can accommodate every way of
approaching things.
In short, I don't think it's a flaw in anything particularly - you have
to accept that no framework is going to be perfect for every
programming paradigm.
--
Jon Skeet - <skeet@xxxxxxxxx>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
.
- References:
- Re: multiple inheritance
- From: Jeff Louie
- Re: multiple inheritance
- From: Jon Skeet [C# MVP]
- Re: multiple inheritance
- Prev by Date: Performance tuning a WinForm app
- Next by Date: Help with XmlNode - HasChildNodes always returns true even no immediate child exists
- Previous by thread: Re: multiple inheritance
- Next by thread: Re: multiple inheritance
- Index(es):