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,XPRIO autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8eff44ec1bcf8433,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-14 13:51:25 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!paloalto-snf1.gtei.net!chcgil2-snh1.gtei.net!chcgil2-snf1.gtei.net!news.gtei.net!news.huji.ac.il!not-for-mail From: "Ehud Lamm" Newsgroups: comp.lang.ada Subject: Container reqs Date: Sun, 14 Oct 2001 22:46:36 +0200 Organization: The Hebrew University of Jerusalem Message-ID: <9qctpn$lil$1@news.huji.ac.il> NNTP-Posting-Host: di3-90.dialin.huji.ac.il X-Trace: news.huji.ac.il 1003092599 22101 132.64.13.90 (14 Oct 2001 20:49:59 GMT) X-Complaints-To: abuse@news.huji.ac.il NNTP-Posting-Date: Sun, 14 Oct 2001 20:49:59 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Xref: archiver1.google.com comp.lang.ada:14486 Date: 2001-10-14T22:46:36+02:00 List-Id: Let's try to make a list of req the Ada community in general can agree on, and than see which of the existing libraries is closest and concentrate on that. (the following are some suggestions) * It seems there is a general agreement to distinguish bouned from unbounded versions. This can be attributed to a more general (non-functional) req: the library should be applicable for RT * I want a library organised around ADT properties (like "sequential access", "set interface" etc) and not around implementations (doubly linked lists). [I think we should think of the best Ada apporach for connecting interfaces and implementations. I explored many of the possibilities, like signature packages, class-wide operations etc., and I am still looking for the best method] * From my experiens the item type is best accepted as a generic paramter (I say this, before anyone suggests and "Object" type, and we start fighting over MI) * The library should offer Algortihms (in STL-speak): sorting, searching etc. * Standard iteration schemes over the various containers (I want both active and passive versions) * Since I am thinking about using the library in education, I'd prefer to make isntantaion as easy as possible (possibly, by supplying pre-instantiated versiosn). I also prefer to hide the tagged nature of interface relationships from casual and first time users. * Memory handling is important, but we don't want to have to do library-level instantaions beacuse of Controlled types. This is not ordered by importance, nor is it a complete list. Let's here more suggestions and critics... -- Ehud Lamm mslamm@mscc.huji.ac.il