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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,9fb7299100a4c4db,start
X-Google-Attributes: gid103376,public
From: dennison@telepath.com
Subject: Abstract realizations can't be inherited??
Date: 1998/08/27
Message-ID: <6s491q$usm$1@nnrp1.dejanews.com>#1/1
X-Deja-AN: 385342888
Organization: Deja News - The Leader in Internet Discussion
X-Article-Creation-Date: Thu Aug 27 18:37:46 1998 GMT
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.05 [en] (WinNT; I)
Date: 1998-08-27T00:00:00+00:00
List-Id: <comp.lang.ada>

I had a situation today where I wanted to declare a new tagged type which is
very similar to an existing one I had. Ahh, classic OO. I just derive it from
the existing type, and redefine the one operation that changed, right? Wrong!

The existing type's operations that I wanted to inherit are overrides of
abstract subprograms inherited from its parent type. The compiler blows up
and points to 3.9.3(6), which appears to say that I have to explicitly
override every abstract subprogram any "ancestor" type has. That means that
if a type is declared abstract, none of the "standard" operations you declare
for it can ever be inherited! What on earth is the logic behind that
restriction?

--
T.E.D.

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum