From: Joshua Ballanco <jballanc@...>
Date: 2009-05-21T02:04:11+09:00
Subject: Re: Pythonic indentation (or: beating a dead horse)

On May 19, 2009, at 5:40 PM, J Haas wrote:

> My friends, when ONE OUT OF EVERY SIX of your code lines consists of
> just the
> word "end", you have a problem with conciseness. I recognize that
> syntactically-
> significant indentation is not perfect, and it would bring a few pain
> points
> with it. But let me say that again: ONE OUT OF EVERY SIX LINES, for
> crying out
> loud! This should be intolerable to engineers who value elegance.
> "Streaks"
> means what you'd expect: there are four places in the scanned files
> that look
> like this:
>
>            end
>          end
>        end
>      end
>    end
>  end
> end
>
> This is *not* DRY. Or anything remotely resembling it. This is an
> ugly blemidh on a language that otherwise is very beautiful.

It's at this point that I started to wonder if you've had a look-see  
at _why's new language, Potion? Specifically:

> * Deeply nested blocks can be closed quickly. I don't like  
> significant whitespace, personally. But I don't like end end end end.
> say = (phrase):
>   10 times (i):
>     20 times (j):
>       phrase print
> _say
> The closing "_ say" ends the block saved to "say" var.