On May 27, 4:32 ¨Βν¬ ΓαμεΓμαυσεΌφιλλ®®®ΐηναιμ®γονχςοτεΊ
> On 5/27/09, Roger Pack <rogerpack2... / gmail.com> wrote:
> >> If you're interested, please see:
> >>http://gist.github.com/117694
>
> > Could you post us a few examples of what code formatted this way looks
>
> Oops, I should have done that when I posted before. Thanks for the reminder.

Fairly awesome. But I think we should consider keeping the colon, and
here's why: blocks that are not delimited by a colon at the start
behave exactly as normal Ruby blocks do, requiring an "end" to close
them, and more importantly ignoring indentation. That way, existing
code can be run through the preprocessor when it's "on", and will
continue to work. And it leaves people to pursue ASCII art with their
indentation, if they are so inclined.

Matz says the colon won't work as a delimiter, though. I'm curious to
know why, but even so, surely something would work.