"Andrew C. Oliver" <acoliver@apache.org> wrote in message news:3D1A1285.2060908@apache.org...
> If I were coding strictly on my own or with
> someone who writes as good of code as Walter does (only perhaps with a
> bit more in the way of comments), then I'd find C++ adequate (like I do
> C).

LOL. Most people hate my code, though I find out about it indirectly.

Walter wrote:
> "Andrew C. Oliver" <acoliver@apache.org> wrote in message
> news:3D1A1285.2060908@apache.org...
> 
>>If I were coding strictly on my own or with
>>someone who writes as good of code as Walter does (only perhaps with a
>>bit more in the way of comments), then I'd find C++ adequate (like I do
>>C).
> 
> 
> LOL. Most people hate my code, though I find out about it indirectly.
> 
> 

True.  I hate Empire.  It wasted much of my time, both directly and indirectly (though the incarnates it influenced).  You wasted my childhood ;-)

But your C++ is good because its limited and doesn't make a big freaking mess (the natural order).  One could work in those constructs and largely avoid the usual problems with C++.  (That is until one had to work with someone who thought for instance that multiple inheritence was cool and used it everywhere they could think of and made a mess of it anyhow).

-Andy

"andy" <acoliver@apache.org> wrote in message news:3D3E9E60.8050704@apache.org...
> True.  I hate Empire.  It wasted much of my time, both directly and
> indirectly (though the incarnates it influenced).  You wasted my
> childhood ;-)

Many years ago, I was accused of causing several students to flunk out because they spent all their time playing Empire.

> But your C++ is good because its limited and doesn't make a big freaking mess (the natural order).  One could work in those constructs and largely avoid the usual problems with C++.  (That is until one had to work with someone who thought for instance that multiple inheritence was cool and used it everywhere they could think of and made a mess of it anyhow).

The only use I ever found for MI was interfacing to some COM code. COM pretty much requires MI, but that capability is handled in D with interfaces.

> Many years ago, I was accused of causing several students to flunk out
> because they spent all their time playing Empire.
> 

Well the game spawned in my opinion the ideas that lead from various games and finally to the ultimate: Civilization and other variants (Civilization spawned directly into about 5+ different games as part of a series not to mention sequals.)  There is even:

http://www.freeciv.org/

I personally consider you to be the root of all evil and indirectly responsible for the current recession. :-)

(I've since cut my addition through having way more work than I could possibly get done.....ever)

> 
>>But your C++ is good because its limited and doesn't make a big freaking
>>mess (the natural order).  One could work in those constructs and
>>largely avoid the usual problems with C++.  (That is until one had to
>>work with someone who thought for instance that multiple inheritence was
>>cool and used it everywhere they could think of and made a mess of it
>>anyhow).
> 
> 
> The only use I ever found for MI was interfacing to some COM code. COM
> pretty much requires MI, but that capability is handled in D with
> interfaces.
> 
> 

Yes.  MI is for extending bad design (COM or really anything on Windows) through other bad design (anything using MI).

Interfaces support the idea that composition is preferred to inheritence.  Interfaces are therefore good.

-Andy

Walter wrote:

> > But your C++ is good because its limited and doesn't make a big freaking mess (the natural order).  One could work in those constructs and largely avoid the usual problems with C++.  (That is until one had to work with someone who thought for instance that multiple inheritence was cool and used it everywhere they could think of and made a mess of it anyhow).
>
> The only use I ever found for MI was interfacing to some COM code. COM pretty much requires MI, but that capability is handled in D with interfaces.

That's the only thing I ever use it for...

Jan

"andy" <acoliver@apache.org> wrote in message news:3D3ED9CB.8080107@apache.org...
>
> Walter wrote:
> >
> > The only use I ever found for MI was interfacing to some COM code. COM pretty much requires MI, but that capability is handled in D with interfaces.
> >
> >
>
> Yes.  MI is for extending bad design (COM or really anything on Windows)
> through other bad design (anything using MI).
>
> Interfaces support the idea that composition is preferred to inheritence.  Interfaces are therefore good.
>
> -Andy
>

In C++, MI is only used with COM because C++ does
not support interfaces. In Delphi COM uses normal
interfaces, no MI.

It is not as bad as you suggest.


--
Stijn
OddesE_XYZ@hotmail.com
http://OddesE.cjb.net
_________________________________________________
Remove _XYZ from my address when replying by mail