Re: How to hide inherited implementation of a public interface?

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Fri, 21 Mar 2014 18:02:28 -0500, Randy Brukardt wrote:

> Full multiple inheritance CAN be implemented, but it's expensive enough in 
> compiler and language complexity that the costs outweight the value.

In the real-life project lack I am working on of proper MI led to a massive
cut-and-paste code explosion on the scale 1 to 1000, at least.

> The 
> halfway Java-like solution is easier to implement but makes no one happy. We 
> should have told the multiple inheritance nuts to forget it, because it 
> makes no sense for Ada.

MI is not a language property, it is more of software design. You cannot
get rid of the fact that software engineers will keep on trying to reuse
code, sharing the code implementing file reading in the code of read-only
and read-write files. This is a sound design. It is the opposite [*] that
does not make sense. If the language does not support sound software design
decisions, well, that is what we call a language flaw.

------------
* The standard library is full of flaws caused by not using MI. From minor
issues that Root_Stream_Type does not implement Limited_Controled, to
massive mess that Character and Wide_Character to don't share common
interface.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de