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-25 22:16:05 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!colt.net!newspeer.clara.net!news.clara.net!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: Thu, 25 Apr 2002 13:05:02 -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> <3CC59ED2.1000803@home.com> <3CC5B286.6FE61551@san.rr.com> <3CC5B9EE.32F3060@san.rr.com> <3CC83282.69C1884F@san.rr.com> NNTP-Posting-Host: dhcp-200-133.miami.pace.co.uk X-Trace: nh.pace.co.uk 1019754303 25971 136.170.200.133 (25 Apr 2002 17:05:03 GMT) X-Complaints-To: newsmaster@news.cam.pace.co.uk NNTP-Posting-Date: 25 Apr 2002 17:05:03 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:23134 Date: 2002-04-25T17:05:03+00:00 List-Id: In the olden days, disk based maps were called "ISAM Files" :-) 1) As long as we have some kind of stream based mechanism to be able to load/store a map or list to a file, this ought to account for *most* uses of the data structures since it has to get pretty big to start causing problems in today's world of cheap & virtual memory. 2) If you want some version of an ISAM file, that's fine, but it *is* a file so it will likely have needs beyond what an in-memory structure would require. At that point, I'd say you'd want to at least have a high level of similarity between the interfaces, but I wouldn't feel the need to have a slavish compatibility between the two. We should put it in our back pocket for another day and just be sure that whatever spec is built for Maps, that it is sufficiently abstract to hide the particulars of the implementation. That really ought to be enough. 3) Speaking of files, couldn't Ada benefit from having a "Standard" RDBMS? There used to be AdaSage, but I don't think it was a generic DBMS thing. I don't even know if it gets much use these days or if it is being actively maintained. Is there something that could be declared "The Conventional Ada Answer" for an RDBMS? MDC -- Marin David Condic Senior Software Engineer Pace Micro Technology Americas www.pacemicro.com Enabling the digital revolution e-Mail: marin.condic@pacemicro.com "Darren New" wrote in message news:3CC83282.69C1884F@san.rr.com... > > While I think this is true of in-memory maps, I think it would be most > excellent if we also had disk-based maps (b-trees, for example) that had > the same package interface. It doesn't have to be there day one, but I > think it's worthwhile double-checking the API to make sure there's > nothing there that implies all the data is in memory at once. >