From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,1116ece181be1aea
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-09-17 23:58:43 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsmi-us.news.garr.it!newsmi-eu.news.garr.it!NewsITBone-GARR!newsserver.cilea.it!news.crs4.it!not-for-mail
From: Jacob Sparre Andersen <sparre@crs4.it>
Newsgroups: comp.lang.ada
Subject: Re: Is the Writing on the Wall for Ada?
Date: Thu, 18 Sep 2003 07:24:22 +0200
Organization: CRS4, Center for Adv. Studies,
 Research and Development in Sardinia
Message-ID: <3F694186.5060709@crs4.it>
References: <mailman.20.1062997816.295.comp.lang.ada@ada.eu.org>
 <q697b.8261$w41.4773@nwrdny02.gnilink.net> <3F5F7FDC.30500@attbi.com>
 <XSR7b.13955$w41.12275@nwrdny02.gnilink.net> <3F6079A9.6080108@attbi.com>
 <uisnz1kw6.fsf@nasa.gov> <3F60E380.4020307@attbi.com>
 <wvbrekyilaxg.fsf@sun.com>
NNTP-Posting-Host: sparre.crs4.it
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: pietro.crs4.it 1063863747 18235 156.148.70.170 (18 Sep 2003 05:42:27
 GMT)
X-Complaints-To: news@nntpserver.crs4.it.
NNTP-Posting-Date: 18 Sep 2003 05:42:27 GMT
User-Agent: Any Browser, HTML 4.01, XHTML 1.0
X-Accept-Language: fo, da, no, sv, is, fr, de, it,
In-Reply-To: <wvbrekyilaxg.fsf@sun.com>
Xref: archiver1.google.com comp.lang.ada:42652
Date: 2003-09-18T05:42:27+00:00
List-Id: <comp.lang.ada>

Olehjalmar Kristensen wrote:
>>>>>>"RIE" == Robert I Eachus <rieachus@attbi.com> writes:

>     RIE> interfaces  and mix-ins.  But  type inheritance  cannot  be from  two
>     RIE> concrete parents,  no matter what  the language--one parent has  to be
>     RIE> abstract. So  anyone who condemns Ada  for not adding  what cannot be
>     RIE> done needs to get a life.
> 
> What do you mean by "concrete parents"?

Although I agree that "non-abstract parents" is the most obvious 
interpretation of "concrete parents", I understood it as 
"data-containing non-abstract parents".

> class a {
> public:
>   void foo();
> };
> 
> class b {
> public:
>   void bar();
> };
> 
> class c: public a, public b{
> };
> 
> Works just fine,

Looks that way to me too.  But if a and b had contained data, for 
example position data in respectively spherical and rectangular 
coordinates (to reuse an earlier example), then you would most likely 
end up in trouble.

Jacob
-- 
Rent-a-Minion Inc. Because good help is so hard to find.