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,fdc75443ea18fb32
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-11-29 10:38:04 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!hammer.uoregon.edu!skates!not-for-mail
From: Stephen Leake <stephen.a.leake.1@gsfc.nasa.gov>
Newsgroups: comp.lang.ada
Subject: Re: Standard Queue status
Date: 29 Nov 2001 13:29:51 -0500
Organization: NASA Goddard Space Flight Center
Message-ID: <uu1vdfn1c.fsf@gsfc.nasa.gov>
References: <yUBM7.7695$4d6.1768979@news11-gui.server.ntli.net>
 <BWq3g0s2usk2@eisner.encompasserve.org>
 <%QRM7.39743$xS6.65958@www.newsranger.com> <9u0qhb$pq5$1@nh.pace.co.uk>
 <u07tltbt28eq1d@corp.supernews.com> <9u0ujd$rhg$1@nh.pace.co.uk>
 <z9aN7.41127$xS6.69040@www.newsranger.com> <ubshlheoj.fsf@gsfc.nasa.gov>
NNTP-Posting-Host: anarres.gsfc.nasa.gov
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: skates.gsfc.nasa.gov 1007058731 20527 128.183.220.71 (29 Nov 2001
 18:32:11 GMT)
X-Complaints-To: dscoggin@cne-odin.gsfc.nasa.gov
NNTP-Posting-Date: 29 Nov 2001 18:32:11 GMT
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
Xref: archiver1.google.com comp.lang.ada:17179
Date: 2001-11-29T18:32:11+00:00
List-Id: <comp.lang.ada>

Stephen Leake <stephen.a.leake.1@gsfc.nasa.gov> writes:

> I'd like to suggest a slightly different approach. 

And here are my votes on these criteria.

> user must be able to get a list package with a single
> instantiation. 

yes.

> lists must be safe (ie no dangling pointers, etc) against _any_ list
> or iterator operation

No. There should be an "Unchecked_Lists" package that is _fast_, and
perhaps another "Checked" version built on top of it.

> lists must be efficient enough for hard real-time use

No. Hard real-time doesn't do dynamic allocation.

> lists must be safe in a multitasking environment

No. Similar to "Unchecked" above.

> lists must not be a tagged type

I could go either way. Making it tagged allows deep copy on a
non-limited list, so I lean that way.

> lists must be safe for assignment (always do deep copy, or don't
> allow assignment).

Yes.

> list elements must not be private

Hmm, I meant "limited private", not "private". And all my others are
stated positively. So let's replace this with:

"List elements must be limited private".

Yes. They force the user to provide a Copy routine, allowing
multi-layered deep copies.

> lists must support elements of any Ada type (private, limited,
> tagged, indefinite)

Yes. But I could relax this one if it really is a hassle.

-- 
-- Stephe