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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,14f7200925acb579 X-Google-Attributes: gid103376,public From: Brian Rogoff Subject: Re: No Go To's Forever! Date: 2000/03/22 Message-ID: #1/1 X-Deja-AN: 600919404 References: <38D7B41D.B3494C6A@lmco.com> <8b8m2e$8201@news.cis.okstate.edu> <8b9fk3$l18$1@nnrp1.deja.com> <38D8DFC2.778826FB@cadence.com> <8barci$4ks$1@nnrp1.deja.com> Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: nntp1.ba.best.com 953744495 211 bpr@206.184.139.136 MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 2000-03-22T00:00:00+00:00 List-Id: On Wed, 22 Mar 2000, Robert Dewar wrote: > In article <38D8DFC2.778826FB@cadence.com>, > Paul Graham wrote: > > > Why is there no 'continue' statement in Ada? You've shown > > that the function of 'continue' is desirable. > > Yes, the *function* of continue is desirable, but on the other > hand a continue is indeed a goto, so why not say so? That's the > other point of view, and as you see from the previous post, > some people find it clearer to use a goto here. We did discuss > this in the language revision but there was insufficient > support for this language addition. I agree with Roger Barnett who wrote that he preferred your "goto" form to C's continue since it made explicit the flow of control. Adding continue to Ada would be a mistake IMO (like adding "use type" was. There, get those flames going ;-) > I guess the burden here is to explain why the goto formulation > is so horrible. Because the great Dijkstra said goto is bad, and therefore it is, at least if it is spelled that way. Dijkstra also wrote that CS students should be kept away from a computer for their first year and focus on pencil and paper proofs (no problem for me, I was a Math major) and he probably didn't like Ada anyways so phooey on him :-) -- Brian