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.0 required=5.0 tests=BAYES_20,FREEMAIL_FROM, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,459feef56669b92d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-11-03 07:47:20 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!fr.ip.ndsoftware.net!teaser.fr!enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail From: "amado.alves" Newsgroups: comp.lang.ada Subject: RE: "continue/next" for "loop" Date: Mon, 3 Nov 2003 15:44:43 -0000 Organization: Cuivre, Argent, Or Message-ID: NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: melchior.cuivre.fr.eu.org 1067874322 24409 80.67.180.195 (3 Nov 2003 15:45:22 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Mon, 3 Nov 2003 15:45:22 +0000 (UTC) To: Return-Path: X-MimeOLE: Produced By Microsoft Exchange V6.0.6470.0 Content-Class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: "continue/next" for "loop" thread-index: AcOiC+M6hWwbEK2XQeC5ESwaF8VQ3gAAzhteAAPsuRM= X-OriginalArrivalTime: 03 Nov 2003 15:40:54.0811 (UTC) FILETIME=[DE4346B0:01C3A220] X-Virus-Scanned: by amavisd-new-20030616-p5 (Debian) at ada-france.org X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Gateway to the comp.lang.ada Usenet newsgroup List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: archiver1.google.com comp.lang.ada:1991 Date: 2003-11-03T15:44:43+00:00 "Sometimes I use exceptions..." I remember some people are against using exceptions for control flow. I = think this even appears in some coding standards. So, as other have said, the goto might be appropriate. Yet another way is to structure the code more, i.e. put the crucial = sequences of statements inside (local) procedures, and then call the = procedures at the appropriate points. Of course you may have to parametrize the procedures to pass the values = of the loop control variables. Come to think of it, this is probably how I do it most of the times. I = seem to remember having really long procedure names...