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,ac39a12d5faf5b14 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-04-22 19:02:57 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!kibo.news.demon.net!demon!psiuk-p2!psiuk-p3!uknet!psiuk-n!news.pace.co.uk!nh.pace.co.uk!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Grace and Maps (was Re: Development process in the Ada community) Date: Mon, 22 Apr 2002 10:37:26 -0400 Organization: Posted on a server owned by Pace Micro Technology plc Message-ID: References: <3CB46975.90408@snafu.de> <3CBAFFEE.2080708@snafu.de> <4519e058.0204171036.6f0a7394@posting.google.com> <3CBDD795.4060706@snafu.de> <4519e058.0204180800.44fac012@posting.google.com> <3CBF0341.8020406@mail.com> <4519e058.0204190529.559a47ae@posting.google.com> <3CC1C6B3.6060306@telepath.com> <3CC21747.5000501@telepath.com> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1019486249 25559 136.170.200.133 (22 Apr 2002 14:37:29 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 22 Apr 2002 14:37:29 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:22947 Date: 2002-04-22T14:37:29+00:00 List-Id: Can the requirements be kept lean enough to be put in the banner of the code? For a widely circulated project, it would be nice to be sure all the important things go along with the code. A separate document could be problematic. I have no objections to doing some requirements first. I think in the case of our relatively small container stuff, there probably are not a really long list of them - but there could be for some other libraries. My suggestions: 1) Maps shall be Stuff That's Cool. 2) Maps shall not be Stuff That Sucks. :-) MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com "Ted Dennison" wrote in message news:3CC21747.5000501@telepath.com... > > > On second thought, we really ought to get some kind of consensus on > requirements before rushing headlong into design. If nothing else, it > will save a lot of arguments. > > Requirements I think ought to be included (using the usual should/shall > language): > > Maps shall provide for key lookup in no worse than O(logn) average time > and O(n) worst case (where n is the # of elements in the map). > > Maps shall provide for creation of a sorted list or array, or traversal > in sorted order, in no worse than O(n) time. (In other words, the map is > kept sorted as elements are added). > > Maps should provide an interface consistent with Lists, as far as is > practicable. > > Comments? > > > >