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 07:08:08 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!hammer.uoregon.edu!skates!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: Standard Queue status Date: 29 Nov 2001 08:47:24 -0500 Organization: NASA Goddard Space Flight Center Message-ID: References: <%QRM7.39743$xS6.65958@www.newsranger.com> <9u0qhb$pq5$1@nh.pace.co.uk> <9u0ujd$rhg$1@nh.pace.co.uk> NNTP-Posting-Host: anarres.gsfc.nasa.gov Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: skates.gsfc.nasa.gov 1007041785 3646 128.183.220.71 (29 Nov 2001 13:49:45 GMT) X-Complaints-To: dscoggin@cne-odin.gsfc.nasa.gov NNTP-Posting-Date: 29 Nov 2001 13:49:45 GMT User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 Xref: archiver1.google.com comp.lang.ada:17165 Date: 2001-11-29T13:49:45+00:00 List-Id: Ted Dennison writes: > To get things back on track, I'd like to ask if there is anything in Nick's > proposal that there is general consensus on putting in the strawman (or we could > take it the other way, if that's what folks want). If you want to look at it, > the package in question is at > http://www.adaos.ukf.net/njr05/scl-lists-unbounded.ads.html . I'd like to suggest a slightly different approach. I would find it useful to have a list of criteria, so that we can judge each candidate by that criteria. For example, one criterium is that the user be able to get a list package with a single instantiation. Other criteria have been proposed, such as "lists must be safe (ie no dangling pointers, etc) against _any_ iterator operation". That criteria separates Ted's strawman from Nick's. If we can all agree on what the criteria are, it will be easier to agree on the package design. The criteria list should mention all of the criteria that have been proposed, and say whether the consensus is to keep it or not. Here are some criteria I remember from this discussion: user must be able to get a list package with a single instantiation. lists must be safe (ie no dangling pointers, etc) against _any_ list or iterator operation lists must be efficient enough for hard real-time use lists must be safe in a multitasking environment lists must not be a tagged type lists must be safe for assignment (always do deep copy, or don't allow assignment). list elements must not be private lists must support elements of any Ada type (private, limited, tagged, indefinite) Ted (or Nick); can you post this list on your web page, and try to keep track of votes for and against each one? -- -- Stephe