🚀 go-pugleaf

Bill said ...

>With templates, however the need for multiple inheritance goes away.  I don't 
>have to use MI to use STL for instance.  

You are mixing inheritence with genericity (however its spelt)! 
I will stand here on my soap box and yell at you  guys to 
think outside the SI/template hashing envelop. You need 
MI for the correct separation of implementation.  By the way,
any C++ professional will have the distinction between private 
and public inherience as the interface/implementation distinction,
along with many other idioms and guidelines, the trouble is there
are few keywords for these 

Rambaugh illustrated a bad case  of SI in  his column a half year
back. 

These technologies applied incorrectly  do lead to bad design
( another said 'poor design leads to poor design').

I'll also stand up for static typed language environments that
enable vital type-checking. I have on many occasions being 
informed by the 'complainer' that I've stuffed up the design. 
The newly C++ library  standard is an exciting development.
....     How many SmallTalk dialects are there?

P.S. I'm here to learn Java. I just get side-tracked when poor 
technique is mentioned.