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,ce0900b60ca3f616 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-07 20:50:28 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!feed2.news.rcn.net!rcn!newsfeed1.earthlink.net!newsfeed.earthlink.net!newsmaster1.prod.itd.earthlink.net!newsread2.prod.itd.earthlink.net.POSTED!not-for-mail Message-ID: <3BEA0F08.AD9AB7C1@acm.org> From: Jeffrey Carter X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: List container strawman References: <3BE29AF4.80804@telepath.com><3BE29BD4.10401@telepath.com><3BE2DB99.B707D409@boeing.com><3BE32A18.18404AD1@boeing.com><3BE443DE.574D669C@acm.org><3BE58FDD.E1FB1815@san.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 08 Nov 2001 04:50:33 GMT NNTP-Posting-Host: 209.86.200.149 X-Complaints-To: abuse@earthlink.net X-Trace: newsread2.prod.itd.earthlink.net 1005195033 209.86.200.149 (Wed, 07 Nov 2001 20:50:33 PST) NNTP-Posting-Date: Wed, 07 Nov 2001 20:50:33 PST Organization: EarthLink Inc. -- http://www.EarthLink.net X-Received-Date: Wed, 07 Nov 2001 20:46:26 PST (newsmaster1.prod.itd.earthlink.net) Xref: archiver1.google.com comp.lang.ada:16036 Date: 2001-11-08T04:50:33+00:00 List-Id: ramatthews@tinuviel.com wrote: > > While I see a foolproof list does not have universal appeal I have > been successfully using one for some time so I thought its > specification would help discussions. How does this extra complexity ensure that the list is foolproof? It is not clear, for example, how this prevents updating a node through one Position (which you call Enumerator_Type) that has been deleted through another. The initial block of comments is rather a lot to digest all at once, and might be better distributed among the type and subprogram declarations it refers to. The use of "current" by itself is a bit confusing; it sounds as if it is a global property of a list, when actually it is a property of a position within a list. Overall, the package looks quite usable. I might suggest a default of Before_Current in the Insert procedure. -- Jeff Carter "Sons of a silly person." Monty Python & the Holy Grail