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,cda33fc7f63c2885 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-01-08 13:49:26 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!out.nntp.be!propagator-SanJose!in.nntp.be!newsranger.com!www.newsranger.com!not-for-mail Newsgroups: comp.lang.ada From: Ted Dennison References: Subject: Re: list strawman 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: Tue, 08 Jan 2002 16:49:18 EST Organization: http://www.newsranger.com Date: Tue, 08 Jan 2002 21:49:18 GMT Xref: archiver1.google.com comp.lang.ada:18670 Date: 2002-01-08T21:49:18+00:00 List-Id: In article , Stephen Leake says... > >Ted Dennison writes: >> Its there, it just hasn't been very well advertised. > >We need to add a explicit visible "=" to make it do what you want; in >my implementation, the default "=" does not. You don't have to override "=" in the public part of a spec, so I usually don't. With the strawmen I took the principle that only the public part of the spec was presented, along with some extra stuff in the private part to get it to compile. Perhaps in this case I took the principle too far... I should shoulder the blame for any confusion this "implicit requirement" has caused, since I left it implicit. But nits aside, it should be clear that "=" is available, for Lists and Iterators, and thus implementors must make them both do the sensible thing. Leaving them available but doing useless things is obviously not good design. I might accept it for a package internal to a project, but certianly not for something that is supposed to be standard. Looking back at it now, what I should have done is what was done in the LRM for the built-in operators in package Standard: put them in the public part commented out. --- 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.