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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,29b1b6650a74a211 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-11-09 11:43:10 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed.icl.net!newsfeed.fjserv.net!kibo.news.demon.net!news.demon.co.uk!demon!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Problem with Booch iterators Date: 09 Nov 2002 19:43:10 +0000 Organization: Pushface Sender: simon@smaug.pushface.org Message-ID: References: <3dcd00f3$0$307$bed64819@news.gradwell.net> NNTP-Posting-Host: pogner.demon.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.demon.co.uk 1036870985 7616 62.49.19.209 (9 Nov 2002 19:43:05 GMT) X-Complaints-To: abuse@demon.net NNTP-Posting-Date: Sat, 9 Nov 2002 19:43:05 +0000 (UTC) User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 Xref: archiver1.google.com comp.lang.ada:30664 Date: 2002-11-09T19:43:10+00:00 List-Id: porton@ex-code.com (Victor Porton) writes: > There are a serious misdesign of Booch iterators: > > Declaring a record component of type Iterator'Class, > I get error "unconstrained subtype in component declaration". > > So for every non-abstract collection type, a concrete iterator > type should be visibly declared. It also suggests that types of > arguments of subrountines should be changed from Iterator'Class > to the appropriate concrete types. > > Simon, why you've used Iterator'Class everywhere? Given the way the BC iterators work, I don't know what good having iterators in records is going to do you. I don't like the idea of unbound iterators floating around (I suppose though it's no worse than a Text_IO.File_Type). I guess I don't see what it is you're trying to do with the BCs that is causing you so much grief. Since there are at least 3 projects using the BCs to earn themselves money (even if I don't see any of it, except indirectly) I won't make backwards-incompatible changes; and I'm reluctant to add operations and features, unless it can be done in a way which doesn't increase the footprint. I would be more inclined to remove things .. BC_Lite, I guess.