>>32
You forget that C and the C subset of C++ are essentially a ``portable assembler.'' It's not supposed to look good, it's supposed to run fast with no or little overhead, once compiled for the target platform. That's what his code does. It's not supposed to look pretty or elegant like Lisp. Just because your sexprs look so clean doesn't mean that it runs fast.
Sometimes you need raw performance, and that's when you get your hands dirty with C or C++ and even a bit of assembly or compiler intrinsics for hardware specific instruction sets.