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,900edaa189af2033
X-Google-Attributes: gid103376,public
From: Andre Spiegel <spiegel@berlin.informatik.uni-stuttgart.de>
Subject: Re: Ada95 OOP Questions
Date: 1996/07/30
Message-ID: <lhmpw5ef46i.fsf@berlin.berlin.informatik.uni-stuttgart.de>#1/1
X-Deja-AN: 170989286
sender: spiegel@berlin.berlin.informatik.uni-stuttgart.de
references: <4tf3l4$4hu@masala.cc.uh.edu>
organization: University of Stuttgart, Germany
newsgroups: comp.lang.ada
Date: 1996-07-30T00:00:00+00:00
List-Id: <comp.lang.ada>


Spasmo writes:

> Well I can live with passing parameters but still the question
> of inheriting operations from a parent class defined in a
> different module is IMO a big deal.

There is no problem with this, whatsoever.  Your inheriting type can be
in a different package than the base type, or in the same package, it
doesn't matter.

(One more thought on the issue of subprograms being a part of the
object: certainly the code of each subprogram exists only once in the
system -- even if there are ever so many objects of the same type.  So
the actual object definitely needs to be passed as a parameter to the
subprogram.  That is true for every OOP language that I know of.)