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,ac39a12d5faf5b14 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-04-22 06:31:46 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: dennison@telepath.com (Ted Dennison) Newsgroups: comp.lang.ada Subject: Re: Grace and Maps (was Re: Development process in the Ada community) Date: 22 Apr 2002 06:31:46 -0700 Organization: http://groups.google.com/ Message-ID: <4519e058.0204220531.3a47ba39@posting.google.com> 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: 65.115.221.98 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1019482306 11383 127.0.0.1 (22 Apr 2002 13:31:46 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 22 Apr 2002 13:31:46 GMT Xref: archiver1.google.com comp.lang.ada:22900 Date: 2002-04-22T13:31:46+00:00 List-Id: Kilgallen@SpamCop.net (Larry Kilgallen) wrote in message news:... > In article <3CC21747.5000501@telepath.com>, Ted Dennison writes: > > > 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? > > While the interface should not _prevent_ implementations from > achieving certain performance goals, I don't think performance > goals should be part of the requirements. If a vendor wants to > provide a relatively slow implementation, that is their choice, > just like their choice regarding how fast A := B'length should > perform. I can see your point. For real-time use its vital to know this. I'd prefer to see it in the requrements that Maps are usable in real-time once the map is already built, which is what these requirements are getting at. Perhaps I am committing the cardinal sin of trying to design with requirements though. -- T.E.D. Home - mailto:dennison@telepath.com (Yahoo: Ted_Dennison) Homepage - http://www.telepath.com/dennison/Ted/TED.html