>>36
Try implementing it in C. Compare. QED
I didn't mean that facetiously. I was serious.
And the funny thing is, that if you did it the superficial way, which would only be about 3x longer (that's a lot!), you'd be missing out on the true power of blocks, since they're closures.
Emulating that in C would not only be a hideously ugly hack, it'd double the length of C code yet again. And since C doesn't have a GC, which is just
kinda necessary for closures, uh... you'll probably end up doing reference counting with explicit free somewhere in the call hierarchy of every function that makes use of the closure. Yeach.
Not very readable any more, is it?