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-10 08:25:13 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeed.berkeley.edu!news-hog.berkeley.edu!ucberkeley!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: <3BECA3B7.5020702@telepath.com> <87668ivpw8.fsf@deneb.enyo.de> Subject: Re: List container strawman 1.2 Message-ID: <_wcH7.20057$xS6.32511@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: Sat, 10 Nov 2001 11:24:26 EST Organization: http://www.newsranger.com Date: Sat, 10 Nov 2001 16:24:26 GMT Xref: archiver1.google.com comp.lang.ada:16221 Date: 2001-11-10T16:24:26+00:00 List-Id: In article <87668ivpw8.fsf@deneb.enyo.de>, Florian Weimer says... >You should not call it a "bounded error" because that would be >confusing. Such errors result in erroneous execution with typical >implementations. For debugging, we might add an additional variable I thought the whole point of "bounded errors" was that they *don't* result in erroneous executions. Instead, there's a certian defined set of nasty things that may happen (vs. the infamous "nasal monkeys" you get when you say "erronious"). >parameter to the generic, which can be used to enable debugging. It >should default to "no debugging", and in such cases, at least GNAT >generates no code for "if Debugging then ... end if;" conditional >statements. That's a technique I have to say I've never used in final production code, and is certianly not used anywhere in the rest of the current Ada library. Exactly what benifit would we get from this? I don't think you can use it to switch between safe active iterators and unsafe "Locations", as the declarations would have to be different too. >Regarding the the name of "Index", I would like to reserve this word >for discrete types. "Location" or "Position", as proposed by Jeffrey, >is probably better. Fair enough. >What about terminating Iterator prematurely using an exception? It's >a bit ugly, granted, but with the "out" parameter approach, I've >managed to forget to set the parameter more than once. If the Quit >parameter is going to stay, we shouldn't use a Boolean type for it, >but a new enumeration type. I suspect we would have some violent objections to that idea from some people (Although its still an option for the user. Just handle it outside the Iterator call). What would you say to the proposal we had to make it "in out" with a default? --- 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.