Can someone explain why /prog/ thinks this is a bad thing? Who the fuck *doesn't* indent their code? And why do we need brackets if the code blocks are already defined by indentation? Makes perfect sense to me.
Can someone explain why /prog/ thinks this is a bad thing? Who the fuck *doesn't* sage fucking stupid posts? And why do we need mods if the fags are already defined by shitty posts? Makes perfect sense to me.
Name:
Anonymous2007-06-25 12:59 ID:D7d1IxgF
Can someone explain why /grog/ tastes like it's a bad thing? Who the fuck *doesn't* like to drink diluted ron? And why do we need to mix ron and water if grog are already bottled by alcohol makers? Makes perfect sense to me.
Name:
Anonymous2007-06-25 14:06 ID:ofQLvfNe
ONE WORD, FORCED INDENTATION OF THE CODE, THREAD OVER!
The first time I saw Forth, the semantics did remind me of points-free function definitions. I guess a theoretical difference to most FP languages is that you can return >1 item, although Scheme does have (values).
The practical difference for me is that I can understand (hence, could try verify and maintain) the source code for a Forth compiler. I'm not smart enough to do that for something like Haskell.
Name:
Anonymous2007-06-26 12:49 ID:8XMUKpjf
>>25
You can return more than one item in Python. For example:
def f(x):
return x, x + 1
def g(x, y):
print "I've got %d and %d" % (x, y)
#Call function saving its values
x, y = f(3)
#Call function capturing its values in a single tuple
x = f(3)
#Call function passing its two results to another function
g(*f(3))
Name:
Anonymous2007-06-26 12:56 ID:jFgDhU5y
>>26
The reason I said it was a theoretical difference is that you can do what you've suggested--return a tuple of N items--in most languages. It's only when you write formal semantics (which most languages don't even bother with) that treating the passing of arguments and return values identically makes things much simpler. Practically, there's very little difference between (values 1 2) and #(1 2).
Drink diluted ron And why do we need mods if the fags are already defined by indentation Makes perfect sense to me.
This is the most sensible post here.
Can someone explain why /prog/ thinks this is a bad thing?
/prog/ sucks Who the fuck *doesn't* indent their code?
/prog/ apparently And why do we need brackets if the code blocks are already defined by indentation?
We don't, FIOC is good Makes perfect sense to me.
Yes, it does