🚀 go-pugleaf

Hi,
    Please don't misunderstand, it's not that I agree or disagree with
whether or not MI is good, expected, etcetera.


MI could have solved some of my programming tasks a lot more
easily than the route I had to go.

I have read arguments in several beginner books pro and con MI.
I would have to become a lot more proficient in C++ to have
the background to make an intelligent decision.

just thinking about it, it seems to me that creating a class library would
take a longer period of time if classes are limited to single inheritance,
so I would guess that decision wasn't lightly made.

but all this is getting away from the original question in this thread,
and doesn't help the guy who is using a tool that doesn't support MI ;-)

"Alisdair Meredith" <alisdair.meredith@uk.renaultf1.com> wrote in message
news:3E677863.21FAFB3@uk.renaultf1.com...
Stephan wrote:

> Part of using the concepts of OOP
> is learning how to tackle a problem in a manner consistent with the
> solution techniques available.

Multiple Inheritance is a standard feature of the C++ language,

VCL is implemented in Delphi, which rejected the idea of multiple
inheritance as something too prone to abuse.

it has long been observed that sharing interfaces is a valuable feature
of OO as exemplified in Java.

We are left with a compiler for a language that supports MI, a class
library implemented in a language that supports multiple interfaces, yet
until last version we were unable to use it, and even now it is somewhat
limited.

I think it was a fair question to ask <g>

--
AlisdairM
Team Thai Kingdom