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,FREEMAIL_FROM autolearn=ham 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 10:35:10 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newshub.sdsu.edu!tethys.csu.net!canoe.uoregon.edu!logbridge.uoregon.edu!msunews!not-for-mail From: "Chad R. Meiners" Newsgroups: comp.lang.ada Subject: Re: "continue/next" for "loop" Date: Mon, 3 Nov 2003 13:33:20 -0500 Organization: Michigan State University Message-ID: References: NNTP-Posting-Host: arctic.cse.msu.edu X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Xref: archiver1.google.com comp.lang.ada:2005 Date: 2003-11-03T13:33:20-05:00 List-Id: "Dmitry A. Kazakov" wrote in message news:bqrcqvscteqbh6s5ta7e1ntqnb9p84km1s@4ax.com... > On Mon, 3 Nov 2003 15:01:52 +0000 (UTC), Lutz Donnerhacke > wrote: > > >It's not a state machine. It's a "parser" which determine the end of the > >current iteration processing at a much deeper level. > > A "parser" isn't that different from FSM. So far your FSM or > whatsoever needs no stack(s) to wind up upon state changing, goto's > are just fine. > > Otherwise it becomes a nigthmare, no matter how you are going to do > it! So stop feeling guilty, and use gotos! (:-)) Agreed, when writing parsers and FSM, I use goto's when necessary. It's much better than if constructs and booleans. -CRM