Else statement executing when it shouldnt

[Jussi Piitulainen]

Thomas Boell writes:

> Using a keyword that has a well-understood meaning in just about
> every other programming language on the planet *and even in
> English*, redefining it to mean something completely different, and
> then making the syntax look like the original, well-understood
> meaning -- that's setting a trap out for users.
> 
> 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".

I believe someone didn't want to introduce a new keyword for this,
hence "else".