Re: "continue/next" for "loop"

[Lutz Donnerhacke <lutz@iks-jena.de>]

* Jeffrey Carter wrote:
> The problem with this discussion is that we don't know what the OP is
> trying to do; we only know how he is trying to do it, sort of.

What: I'm writing teaching programs for a security class.
How : I'm writing readable programs for a security class.

> As pointed out elsewhere, the goto's could be converted to "exit Inner;"
> and the statements between "end Inner;" and "end Outer;" removed, with no
> change in behavior, so we don't really even know how the OP is trying to
> do whatever he is trying to do. If we knew what he was trying to achieve,
> rather than how he was trying to do it, we might be able to propose an
> alternative approach that would avoid his problem.

Sorry, that I does not include the source code of the upcomming exercise now.
I only noticed a missing language expressivity and asked about my dumbness.

> Assuming some way to exit Inner and execute the statements between the 
> end of Inner and the end of Outer, we have seen a number of ways to 
> achieve this: goto statements, a Boolean flag, and exceptions. Another 
> way is to use a dummy loop and exit it:

All those ways are possible, but they lose readbility.