WTF is wrong with forced indenting? It's a habit you should already be into if you write any piece of code. Ever tried to read code that isn't indented or spaced? Thats right mother fucker, it's next to impossable.
Suck my cock you scriptkiddy.
Name:
Anonymous2007-12-13 7:14
I see I have finally gotten on your nerves. Well, I might as well admit that I really lurve Python.
Name:
Anonymous2007-12-13 7:16
>>1
ah, but sometimes forced indentation can really mess with one's comments in certain situations
>>1
Ever write any code for any serious software? No, in the real world, style/indentation, singletons, MVC, "design patterns" and all that shit are just guidelines.
Of course, though, you DiveIntoPython programmers know more than we do.
Forced indentation is also in the way when doing arbitrary indentation like that between glBegin() and glEnd() calls. Ever looked at OpenGL code written in Python? I have. It looks like shit.
Name:
Anonymous2007-12-13 7:46
>>8
if you still use immediate mode like that youre an idiot
Name:
Anonymous2007-12-13 8:11
At least I can still reformat brace-delimited code that's been deprived of indenting, but with a FIOC language the whole meaning is destroyed.
Name:
Anonymous2007-12-13 8:28
>>1
I actually invented that meme. It all started out when I was trolling the ``Bad Things about Python'' thread.
NB: This post was typed entirely in DVORAK, the superior keyboard mapping.
Name:
Anonymous2007-12-13 8:39
>>4
Well, if you are in the middle of a switch statement, and wish to have a comment to break up the cases, i've seen it where the comment ends up being a total penis.
something like this in a pseudo language similar to c -
switch(s) {
//Lower-case cases
case 'a'
//handle 'a'
handlea();
break;
case 'b'
//handle 'b'
handleb();
break;
case 'c'
//handle 'c'
handlec();
break;
//Upper-case cases
case 'A'
//handle 'A'
handleA();
break;
case 'B'
//handle 'B'
handleB();
break;
case 'C'
//handle 'C'
handleC();
break;
}
The 2 major comments regarding the groupings of the cases get indented, but I wouldnt want them there. Id want them in line with the case labels
Name:
Anonymous2007-12-13 8:48
linus says your not supposed to have an indent before the cases. although linus seems to be an opinionated cocksucker.
Name:
Anonymous2007-12-13 8:49
>>12
Python has no problem with comments being indented further than the code.
Name:
Anonymous2007-12-13 8:50
>>13
Linus can go fuck himself. Just because he cobbled some minix clone together doesn't make him an expert on code aesthetics
with drawing(GL_TRIANGLE_FAN):
for x in xrange(0, steps):
angle = x * (math.pi / (steps / 2))
glVertex2f(math.cos(angle) * radius,
math.sin(angle) * radius)
Name:
Anonymous2007-12-13 10:22
Yeah, it puts the pointer asterisks in the wrong place (a space after the first half of the type, and no space before the pointer modifiers or the variable name), but I believe this is very much like my style otherwise. % cat .indent.pro
-bad
-bap
-bli0
-br
-cbi0
-ci0
-cli0
-i4
-npcs
-lp
-ts4
-ut
-psl
Name:
Anonymous2007-12-13 10:36
(somevariable * (someothervariable - 1) + 1)
+
(yetanothervariable * someothervariable + 1)
or big if statements or big function calls or...
The problem is that Python thinks it knows it better than the programmer. This makes it the preferred language for idiots, and is the reason EXPERT PROGRAMMERs hate it.
Name:
Anonymous2007-12-13 10:45
>>18
Most of the actual EXPERT PROGRAMMERS I've seen commenting Python seem to like it very much.
Name:
Anonymous2007-12-13 11:24
>>19
Most of the actual EXPERT PROGRAMMERS you've seen only know more than you but actually suck shit
Name:
Anonymous2007-12-13 12:20
>>16
>>> from __future__ import braces
SyntaxError: not a chance (<pyshell#8>, line 1)