Re: "continue/next" for "loop"

From: Chad R. Meiners (crmeiners_at_hotmail.com)
Date: 11/03/03 

Date: Mon, 3 Nov 2003 13:33:20 -0500

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> wrote in message
news:bqrcqvscteqbh6s5ta7e1ntqnb9p84km1s@4ax.com...
> On Mon, 3 Nov 2003 15:01:52 +0000 (UTC), Lutz Donnerhacke
> <lutz@iks-jena.de> 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