Re: stopping a loop iteration without exiting it

["Jeffrey R. Carter" <spam.jrcarter.not@spam.not.acm.org>]

On 01/05/2018 08:13 PM, Paul Rubin wrote:
> 
> If a construct is useful, then the existence of an ugly workaround for
> its absence doesn't make it non-useful.  Of course it's not "needed"; as
> Mart van de Wege says, you could use GOTO for everything so none of it
> is needed.  The question is whether it improves code readability,
> reliability, developer productivity, etc.

When I say "needed", I of course mean needed to make the code significantly 
simpler or clearer than code without the "continue". In fact, my experience has 
been the opposite: excluding the majority of uses, which are equivalent to an 
"if" and are equivalent in simplicity and clearness, the real-world examples 
I've seen where people wanted or used a "continue" were simpler and clearer when 
reworked to avoid the "continue".

I'm willing to accept that there are cases where the construct would result in 
simpler or clearer code. People have claimed to have such cases, but I have not 
seen them. But based on my experience, there is no need for such a feature.

-- 
Jeff Carter
"What's the amount of the insult?"
Never Give a Sucker an Even Break
104