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-14 06:31:20 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!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> <5DaI7.23016$xS6.35866@www.newsranger.com> <3BF15C70.B7EF23E6@san.rr.com> <3BF19106.5FF19B59@san.rr.com> <3BF1A5FC.251D9F20@san.rr.com> Subject: Re: List container: Insert and Delete 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: Wed, 14 Nov 2001 09:31:15 EST Organization: http://www.newsranger.com Date: Wed, 14 Nov 2001 14:31:15 GMT Xref: archiver1.google.com comp.lang.ada:16499 Date: 2001-11-14T14:31:15+00:00 List-Id: In article <3BF1A5FC.251D9F20@san.rr.com>, Darren New says... > >Ted Dennison wrote: >> is the case, the general rule ought to be to leave the function out, unless >> it is something so common that just about any disinterested observer would be >> suprised to not find it in there. > >Sure, as long as stuff like that *can* be done. Right. I can certianly see occasions where we might want to include an O(NlogN) function because implementing it yourself with the other tools provided might be O(N**2), or not even possible at all. >Yes. My concern was that *if* the "position" type can't be compared for >equality by the user, you have to provide that in the library somehow. >*Then* it becomes a one-liner to translate to integers and back. Right now its not limited, so "=" is available. That being the case, I'd think "=" ought to do something sensible (or be taken away). An incarnation or two ago, iterating even depended on it. --- 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.