Re:I don't like Python. Does that make me a bad person?
by maw on Sunday June 27, 2010 @09:42AM
(#1465468)
If you write code like this:
if x:
# do stuff
# do other stuff
In languages whose blocks are closed using nonwhitespace the problem doesn't exist. Your indenter just has to push everything as far to the right as it can, and problem solved.
It's nice that your editor gets copy and paste right, but it doesn't and indeed can't decide how to indent your code, something that works in every other language I've dealt with.
Re:I don't like Python. Does that make me a bad person?
by crystalis on Sunday June 27, 2010 @08:24PM
(#1466608)
Why does that matter?
In brace language:
if (condition) {{ code_1 }} code_2
In Python:
if (condition):\n code_1 \n^H code_2
Unless your editor also knows when to place your close braces, and, haha, it doesn't and indeed can't, you have not even won a keystroke.
Re:I don't like Python. Does that make me a bad person?
by maw on Tuesday June 29, 2010 @03:52PM
(#1472546)
Once I've placed my closing braces, I'll never need to think about it again, unless and until I restructure that piece of code.
It's got nothing about saving keystrokes.
And now, back to working on pass-infested Python code.
To my knowledge, this is no worse than the expectation for a braced language, but much better than the worst case for a braced language.
If you mean something simpler than I've taken you to mean, e.g., the conversion of a whitespaceless C program into a whitespaced one, I concede you are mostly correct (';' still works in Python), but I must admit I would still not yet see your point.