>>7
You need to have a ':' on the first row, or it won't parse properly.
Also, you need to have a ':' on the second row, or it won't parse properly.
Third row looks fine though, good job!
if you in (depressed, sadness, resignation):
print 'me, my sweetheart'
if feel(you) is 'lonely' or feel(you) is 'neglected':
talk_me(this)
while always:
I.take_care(you)
if you.love() is not me:
# I will follow in the madness
# I will
break # down...
for emotion in my.heart:
try:
your.lover = me
except:
your.best_friend = me
if you.hate(me):
love(me)
elif I.annoying():
love(me)
else:
love(me, how='deeply', when='now')
Name:
Anonymous2006-12-07 18:16
>>7
What is this faggotry? slapPosters :: [Poster] -> IO ()
slapPosters ps = (mapM_ (slap) (filter ((== 5) . posterNumber) ps))
Text on the line after a code block.
>>14
That's ok though; languages are only supposed to be used by those who actually know them.
Name:
Anonymous2006-12-08 7:16
>>17
Being able to understand it with general programming knowledge, but without specific knowledge of that language, tells something about the design quality and goals of a language.
>>18
I find it better to read the language's formal specification rather than second-guessing. I haven't been able to track down Python's design docs yet, but then again I haven't been trying very hard.
python is nice because I can write half of it in C anyway. It's like... the best of both worlds. All the shitty GUI stuff gets done in python in record time, and all the business logic done in C so it doesn't eat 5% of my CPU to add a few hundred numbers.
Name:
Anonymous2006-12-11 15:05
>>35
reduce(int.__add__, xrange(500)) takes about 0.000 seconds
Name:
Anonymous2006-12-11 16:11
>>36
Does it just get replaced by its result during preprocessing?