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,1f0bebbd5edf4a6f
X-Google-Attributes: gid103376,public
From: Brian Rogoff <bpr@shell5.ba.best.com>
Subject: Re: Please help a newbie with Booch/Ada.
Date: 1998/09/01
Message-ID: <Pine.BSF.4.02A.9809011511030.115-100000@shell5.ba.best.com>#1/1
X-Deja-AN: 386927974
References: <35DCCE3A.9EAE78D8@pacbell.net> <upvducc1i.fsf@gsfc.nasa.gov>
 <m3g1eer5uf.fsf@mheaney.ni.net>
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Trace: 904688193 2099 bpr  206.184.139.132
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 1998-09-01T00:00:00+00:00
List-Id: <comp.lang.ada>

On Sun, 30 Aug 1998, Matthew Heaney wrote:
> Stephen Leake <Stephen.Leake@gsfc.nasa.gov> writes:
> 
> > Better would be to fix the Ada 95 Booch components to allow indefinite
> > types. Find the declaration of Bc.Containers, and add "(<>)" as a
> > discriminant to the object type. Be aware this might break lots of
> > stuff; I haven't tried it.
> 
> ... snip ... 
> 
> A component library can't be all things to all people.  Better is to
> provide a small-ish set of primitives from which clients can compose
> their own custom-built abstractions.
> 
> Making all the containers take indefinate subtypes would be the worst of
> all possible decisions, because that would mean _every_ instantiation
> would use heap, even those clients that have definate subtypes.

I agree, but let me note that when a library provides a set of reusable 
generic signatures, I think its a good idea that the parameters to those
signatures be as general as possible, which may mean generic formal 
indefinite limited private types (what a mouthful!).

-- Brian