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,a5d76152c5cb8790
X-Google-Attributes: gid103376,public
From: Francois Godme <fgodme@magic.fr>
Subject: Re: class-wide objects
Date: 1998/12/12
Message-ID: <3671A689.9815C6E0@magic.fr>#1/1
X-Deja-AN: 421356855
Content-Transfer-Encoding: 7bit
References: <366B1190.C8142307@magic.fr> <m3emqc689e.fsf@mheaney.ni.net>
 <366EE6BA.7D586BDD@magic.fr> <m31zm84g2m.fsf@mheaney.ni.net>
 <u1zm6bc9j.fsf@gsfc.nasa.gov>
X-Client: Magic On Line [unknown@ppp10-119.magic.fr]
Content-Type: text/plain; charset=us-ascii
Organization: very little
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1998-12-12T00:00:00+00:00
List-Id: <comp.lang.ada>

Stephen Leake wrote:

> Another way to make an operation non-primitive is to use 'class:
>
> function Copy (Stack : Stack_Type'class) return Stack_Access;
>
> I've been flip-flopping about which way is "best". Using 'class
> sometimes implies re-dispatching in the body, but not always. If the
> non-primitive operations belong in a group (like Constructors), then
> the local package seems neat. But for other operations, a local
> package is just noise, and 'class seems preferable.
>
> -- Stephe

I agree entirely. I do the same as you do.