Actually indenting is always significant, if you are working in a
team.
Noone wants to read unindented code, but I understand the
difficulties you are
talking about. At work I am programming without a braille device at
the moment
and that is not the easiest way, but I can handle it... thank you
emacspeak.
emacspeak was what I was using before I got a Mac. Unfortunately,
there doesn't seem to be any adequate synthesiser to use under OS
X, and I don't have the space to duel boot the machine with Linux,
so I had to ditch it.
Not to mention the fact that, even if it was, the standard in Ruby
seems to be *2* spaces, a much more useful thing.
I can imagine another work-around for problems like that. What
about writing
code without indentation and running a script afterwards, which
indents it
propperly? Same works for the different direction. Take some
indented code and
unindent it, so you can handle it. Any opinions?
this works for most languages, and I usually do run something like
this on my code, even if I *do* think I've got the indents right. I
can't be bothered checking the whole file to be sure.
The problem with *python* though, is that whitespace is what is used
to indicate the beginning and end of things, like functions, classes,
loops etc. In other words, it's an integral part of the syntax. If
you write Python like that, it won't even *run* <grin>.
As a result, writing a code cleaner for python would be quite hard,
since there'd be no easy way to tell what started and ended where.
