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,92c39a3be0a7f17d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-12-31 21:26:42 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!fu-berlin.de!uni-berlin.de!ppp-1-6.cvx6.telinco.NET!not-for-mail From: "Nick Roberts" Newsgroups: comp.lang.ada Subject: Re: Containers package (Tenet) Date: Mon, 31 Dec 2001 23:19:51 -0000 Message-ID: References: NNTP-Posting-Host: ppp-1-6.cvx6.telinco.net (212.1.156.6) X-Trace: fu-berlin.de 1009862800 23828685 212.1.156.6 (16 [25716]) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Xref: archiver1.google.com comp.lang.ada:18417 Date: 2001-12-31T23:19:51+00:00 List-Id: Tenet's going to based on: a design for iterators which I have sent to some people privately for comment, based on a proposal I made to the ASCL project two years ago; my proposal for list containers (V6R1), as amended based on comments by Ted Dennison, Jeff Carter, and others (to whom thanks); a 'common sense' design for sets, lookups (content-addressed arrays, aka associative arrays); maps (a variation of lookups); a few extra bits and bobs (under the name "Workbench"). Each container will come in bounded and unbounded forms. Tenet is not going to have user-defined memory management (storage pools); users who need this level of control and sophistication can use Booch. The only concurrent containers Tenet will provide are queues and bags; the other containers will be suitable for having concurrency control wrapped around them. I'll supply a sample implementation of the whole library, but this will (initially) be aimed more at debugging than efficiency. I'll try to make the documentation fairly good. These are the things I need as a utility base for AdaOS, so that will provide any bias for their design. Other than that, I intend the design to be as general-purpose as possible. -- Best, Nick Roberts