From: J Haas Date: 2009-05-21T03:35:08+09:00 Subject: Re: Pythonic indentation (or: beating a dead horse) On May 20, 8:51 am, Rick DeNatale wrote: > Seriously, if you measure things by avoiding extra keystrokes, get a > better editor.  I value readability over parsimony of lexical items. Cluttering up your code with "end" everywhere makes it less readable, not more. On May 20, 9:01 am, "Michael Bruschkewitz" wrote: > I have some suspicion this was a joke thread. > (Hint: Format of OP) Nope, I'm sincere. As I said before, I'm new. The formatting was a misguided attempt to make things look nice by manually wrapping them at 80 columns. Oops. > This sort of structuring pieces of code stopped me from trying Python > seriously. And I specifically addressed this in my OP. A lot of engineers who haven't done work in Python think that the idea of giving syntactical significance to whitespace is a ridiculous idea. I used to be one of them. Now I know better. Don't knock it until you've tried it. > Isn't there an Syntax-Highlighting Editor out there which allows assigning > 1-Point size to End-Only-Lines? Aside from the fact that this wouldn't solve the problem that I'd still have to _write_ the damned things, this is possibly the kludgiest solution imaginable. > Wouldnt this be the easiest way to solve your problem? The easiest way to solve _my_ problem would be for me to use one of the preprocessing scripts that impose Python-like indentation syntax on Ruby. But that wouldn't solve the larger problem, which is that Ruby could be better than it is. On May 20, 10:04 am, Joshua Ballanco wrote: > It's at this point that I started to wonder if you've had a look-see > at _why's new language, Potion? Nope. but I'll check it out. Thanks.