I love it. It's widely used, easy to understand, and it has everything you need built-in(and hundreds of modules that extended it further if you must). Forced indentation really isn't an issue, and never was. Like you're not going do be indenting your code?
The only real downsides are the lack of a proper case statement and I guess speed, but honestly on today's computers unless you're working with hardcore game development or speed critical applications, it's really not that big of a deal.
kthx bring on the trolls.
Name:
Anonymous2009-03-27 22:50
>>1 today's computers
What about tommorow is computers?
Name:
Anonymous2009-03-27 23:13
>>1 everything you need built in
I need metaprogramming. Back to your scripting ghetto, please!
>>10
What, because you pass code as a string as an argument? That's your big example? eval serves that need amply, and lambdas, which Python has, would do much, much better.
contents of lol.py:
f = open('lol.py')
eval(f.read())
Name:
Anonymous2009-03-28 22:31
>>9 (loop for i from 0 below 10 collecting (* i 10)) Meta!
Name:
Anonymous2009-03-28 22:39
>>11 eval serves that need amply, and lambdas, which Python has, would do much, much better.
No, they wouldn't. If you hadn't noticed he asked for real world applications. setTimeOut() and setInterval() are the most widely used (by several orders of magnitude) metaprogramming constructs.
>>15
Why are you incoherent? Read, and then formulate a relevant reply.
Name:
Anonymous2009-03-28 23:05
>>17 Why are you incoherent?
Funny, not only is this in itself incoherent, the sentence adjacent to it is also. In fact, you should probably be thanking me for even trying to decipher the bumbling mess of text you produced.
Name:
Anonymous2009-03-28 23:13
>>11
Don't you feel a little retarded suggesting that metaprogramming is best accomplished by calling an interpreter? That would be slow as fuck. I can only conclude that bitches don't know about my inner loops. Compile-time code generation or GTFO.