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.6 required=5.0 tests=BAYES_00,TO_NO_BRKTS_FROM_MSSP autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4c8458572136e831 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-09 09:25:18 PST Path: archiver1.google.com!news2.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!arclight.uoregon.edu!enews.sgi.com!news-out.spamkiller.net!propagator-la!news-in-la.newsfeeds.com!newsranger.com!www.newsranger.com!not-for-mail Newsgroups: comp.lang.ada From: Ted Dennison References: <9sdpku$eu2$1@news.huji.ac.il> <9semrm$i79$1@nh.pace.co.uk> Subject: Re: List Containers - The Road Ahead Message-ID: X-Abuse-Info: When contacting newsranger.com regarding abuse please X-Abuse-Info: forward the entire news article including headers or X-Abuse-Info: else we will not be able to process your request X-Complaints-To: abuse@newsranger.com NNTP-Posting-Date: Fri, 09 Nov 2001 12:20:17 EST Organization: http://www.newsranger.com Date: Fri, 09 Nov 2001 17:20:17 GMT Xref: archiver1.google.com comp.lang.ada:16143 Date: 2001-11-09T17:20:17+00:00 List-Id: In article <9semrm$i79$1@nh.pace.co.uk>, Marin David Condic says... > >Maps should look as much like lists as possible. Similar names & >functionality. It might be better to defer Maps until some kind of decision >is taken about lists. >"Ehud Lamm" wrote in message >news:9sdpku$eu2$1@news.huji.ac.il... >> >> That's for lists. >> To see how the universal the design can be, can someone propose a >> Map/Dictionary Strawman? I'd say that we should at least finish getting the kinks out of the iterators before trying to synthesize a "Maps" package, since it will need them too. I started with Lists for 3 reasons: 1) I've implemented a lot of simple ones myself over the years (there are at least 2 in OpenToken), so I have a bit of experience and could do it quickly. 2) I think lists and maps should look consistent, so much of the work in figuring out how the Maps package works would be done in the process of getting Lists nailed down. 3) I didn't think that our discussion of Maps had really progressed to that point yet. I still don't think we are quite there yet, but it may be time to start talking more seriously. For one small example: What is the general opinion about using private "key" types in the Maps generic? Remember that this will mean that "<" is not available. Perhaps that's OK if we provide a boolean comparison routine as another generic parameter, although that raises the complexity a bit. But then, should we attempt to make that parmemter consistent with what is done for the "Sort" routine? How exactly? We also have yet to have the discussion where someone wants "keys" to be their own generic package/type that then gets passed into "Sort" generics and into Maps, and hasn't considered how this complicates use. :-) --- T.E.D. homepage - http://www.telepath.com/dennison/Ted/TED.html No trees were killed in the sending of this message. However a large number of electrons were terribly inconvenienced.