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,a644fa9cd1a3869a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-13 07:03:33 PST Path: archiver1.google.com!news1.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!hub1.nntpserver.com!nntp-relay.ihug.net!ihug.co.nz!out.nntp.be!propagator-SanJose!in.nntp.be!newsranger.com!www.newsranger.com!not-for-mail Newsgroups: comp.lang.ada From: Ted Dennison References: <9sn4qm$13g29j$2@ID-25716.news.dfncis.de> <9sok8i$142am0$2@ID-25716.news.dfncis.de> <3BF004F4.F74AE461@boeing.com> <9sp5up$g5o$1@nh.pace.co.uk> <3BF0827A.DCF2213C@acm.org> <9sra40$b8p$1@nh.pace.co.uk> Subject: Re: List container: Insert and Delete Message-ID: <5DaI7.23016$xS6.35866@www.newsranger.com> 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: Tue, 13 Nov 2001 10:03:29 EST Organization: http://www.newsranger.com Date: Tue, 13 Nov 2001 15:03:29 GMT Xref: archiver1.google.com comp.lang.ada:16409 Date: 2001-11-13T15:03:29+00:00 List-Id: In article <9sra40$b8p$1@nh.pace.co.uk>, Marin David Condic says... > >False. But I see no need that a Bounded package and an Unbounded package >have to be plug compatible. You very seldom would want to unplug the one and I'd agree with this. The only compelling reason I could see for it would be if we were using some kind of root tagged type to implement both (which we aren't), and wanted to allow for dynamic dispatching on classwide list pointers. I'm curious what people think about the extent of the compatability they should have though. Should the look mostly alike, except for routines that don't make sense in that context? Should we remove all basic-looking routines from either implementation with time behavior >=O(N). Should the interface for bounded be completely redesigned around things that you can do with bounded implementations that you can't easily do with unbounded ones? Personally, I think I'm leaning towards the middle-of-the road option, but its not a strong leaning. >plug in the other - you take the decision at the time of design and use the >package that makes most sense then. Swapping implementations after that >would mean some serious regression testing of the software, so you could >probably modify it for any incompatibilities along the way and not be that >bad off. > >I think it was Mark Twain who said something about "A foolish consistency is >the product of little minds." :-) > >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/ > > >"Jeffrey Carter" wrote in message >news:3BF0827A.DCF2213C@acm.org... >> >> The difference, of course, is that you can provide an Is_Full function >> for a bounded list, but not for an unbounded list. In both cases an >> exception should be raised if an attempt is made to add an element when >> that is not possible. >> > > > --- 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.