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=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8eff44ec1bcf8433 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-15 08:46:53 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!psinet-eu-nl!psiuk-p4!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Container reqs Date: Mon, 15 Oct 2001 11:36:22 -0400 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: <9qevpn$8k$1@nh.pace.co.uk> References: <9qctpn$lil$1@news.huji.ac.il> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1003160183 276 136.170.200.133 (15 Oct 2001 15:36:23 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 15 Oct 2001 15:36:23 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Xref: archiver1.google.com comp.lang.ada:14539 Date: 2001-10-15T15:36:23+00:00 List-Id: What would be wrong with starting with a simple set of data structures that got 90% of the work done and then expanding the requirements as experience demands? For example: Why not produce a set of packages that supports a) a homogeneous bi-directional list and b) a homogeneous map? I'll concede to the need for a static & dynamic version of each. That would be what gets called in the technical papers "A Good Start"(tm). It probably should have a handful of sorting & searching algorithms for arrays as well. (Anything else you want to sort & search on a regular basis?) My feeling is that if the scope were kept to something simple and functional for a large majority of uses, it is more likely to get implemented and used. Packages with more options, more parameters, different behaviors, heterogeneous content, sufficient OO-ness, less used structures, etc. can all be added later. MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com Web: http://www.mcondic.com/ "Lutz Donnerhacke" wrote in message news:slrn9slt9m.i2.lutz@taranis.iks-jena.de... > * Ehud Lamm wrote: > >* 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) > > type Item is (<>) tagged abstract limited private; > > in order to build collections of tasks and more. > > type Item is exception; > > *grin* > > Bute seriosly it's necessary, that the same item occurs in several > collections at once. It must be possible to build stacks of lists and hold a > task element in a list and a hash simultaniously. Good luck. > > >* The library should offer Algortihms (in STL-speak): sorting, searching > > etc. > > Of course ... provide algorithms with different size/time constraints. > _Prove_ them correctly and derivate the size/time constraints. > Do not assume special derivations for those algorithms, so allow algorithms > over native Ada types. > > >* Standard iteration schemes over the various containers (I want both active > >and passive versions) > > Keep them threadsafe and multiaccessed, i.e. allow the usage of active > Iterator to create further Iterators which in turn modify the structure. > > >* 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). > > Exactly. > > > I also prefer to hide the tagged nature of interface relationships > > Tagged nature?