proc Fibs take nth. define i = 1 as Integer. define a = 0; b = 1; c = 1 as Natural. loop while i "LESSTHAN" nth do c :- a + b. a :- b. b :- c. done. return c. corp.
Name:
Anonymous2014-12-29 23:11
>>15 I am disappointed that done is not pool instead.
Name:
Anonymous2014-12-29 23:44
>>15 corp and done are just different versions of end.
I actually like significant whitespace. My code is always properly indented anyway. Why do you guys dislike it so much? Making a parser for a grammar with significant whitespace certainly isn't the most fun activity to perform after a long day of work, but it's not like you have to write parsers everyday.
>>20 You god damn fucking little faggot, I am not >>12ramen, not even close. It amazes me what a stupid and worthless little twat you are, pretending like you're Admin-kike-kami-kohai himself and can see my IP address or some shit. Now you failed and everyone knows. You pulled down your pants to show off how huge your 10cm dick is and now everyone is laughing their asses off not only at your tiny cock that may as well not even exist, but at the fact that you are such a delusional retard that you thought it was big. You're the fucking laughing stock of /prog/, you know? You're a fucking joke to us, and trust me, we are laughing at you, not with. No one likes you. No one respects you. No one wants to see your posts or read your opinions on anything at all. Can't even tell people apart. So fucking pathetic.
Fag.
Name:
Anonymous2014-12-30 4:05
>>24 That's why I suggested OCaml instead of F-octothorpe.
Prove that all the possible block delimiters either belong to the begin/end family of explicit delimiters (this includes function end, ((( ))), {{{ }}}, proc corp) or are significant whitespace.
>>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.
>>40 That's actually a clever one, never thought of that. Seems kind of awkward for use in a non-toy language though.
Name:
Anonymous2015-01-01 9:46
>>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
Name:
Anonymous2015-01-01 14:59
>>47 might as well use significant whitespace, dumbfuck
Name:
Anonymous2015-01-01 15:29
>>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.
>>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.