I GET IT, ALL BLOCK-DELIMITING SYNTAXES ARE SHIT

Significant whitespace is shit.
Brace/end hell is shit.
))))) is shit.

What the fuck do you faggots propose then?

>>37
j = 0 ;0
for int i = 1, i < 5, i++ ;0
print "awk is anal-touring complete" ;1

>>40
Would you use that syntax non-ironically?

>>40
Nice one.

>>42
I've written a fair amount of Fortran 77, and compared to that I don't think this is actually any worse. At least if the parser is strict about where you put the indentation labels (ie. always at the beginning of a line) you get a clear indication of where it changes.

>>44
0: print "your"
0: print "language"
0: print "a"
0: print "shit"

>>40
That's actually a clever one, never thought of that. Seems kind of awkward for use in a non-toy language though.

>>46
It's not awkward, you can combine it with whitespace since it's insignificant:

0: j = 0
for int i = 1, i < 5, i++
1: print "Sucking cocks: "
for int k = 1, k <= i, k++
2: print (k + ", ")
1: print "!\n"
j += 2
0: print j

>>47
might as well use significant whitespace, dumbfuck

>>48
No, might not. Because that way it's not significant and then it would be significant. Kind of like the difference between Lisp formatted with indentation (which it usually is) and Python. Sure, Lisp looks like it has significant whitespace, but it actually doesn't, so it's possible to format it the other way. Python? You're locked into that formatting and no other.

God, you're so retarded. How do you manage to use a computer.

I'm reminded of

{ j = 0
; for(int i = 1; i < 5; i++)
{ print("Sucking cocks: ")
; for(int k = 1; k <= i; k++)
{ print(k + ", ")
;
} print("!\n")
; j += 2
;
} print(j)
;

>>42
You could let an editor do the work for you with nest/unnest keys

you're all (((gay niggers)))

>>52
From outer space?

>>1
Use a programming language with a regular grammar.

check em

>>14
i've never had a problem reading C with nested loops like this. just make sure your tabstops aren't tiny.

(((gay niggers))) from bell labs!

>>42
Actually, this is better than FIOC or whatever else.

Say you had to increase the level of indentation by one level. Source control program like Git will mark all lines within the block as changed. However, if you just modify the indentation level symbols, then those lines won't get marked as modified. Combine this with an intelligent editor which will automatically parse and visualize indentation symbols without actually adding whitespace in the buffer, as well as a simple key combination and script to facilitate quick un/indentation, and you would probably use fewer keystrokes than adding in braces everywhere.

>>58

Say you had to increase the level of indentation by one level.

(Using a normal block delimiting syntax that has whitespace at the beginning of each line, whether or not it's insignificant.)

))))) is good

)))))) is best
)];)});)]); is worst
end is laughable

parens are objectively the best way to represent syntax trees