Else statement executing when it shouldnt

[Jerry Hill]

On Wed, Jan 23, 2013 at 8:35 AM, Jussi Piitulainen
<jpiitula at ling.helsinki.fi> wrote:
>> The feature isn't bad, it's just very, very badly named.
>
> I believe it would read better - much better - if it was "for/then"
> and "while/then" instead of "for/else" and "while/else".

That's always been my opinion too.  I'd remember how the construct
worked if it was for/then (and while/then).  Since seeing for/else
always makes my brain lock up for a few seconds when I'm reading code,
I don't bother using it.

Jerry