Then post an unfubbed version of the code, complete with comments on what it's doing.
Because I've just spent a half hour going through it, indenting it for human comprehension.
There's clever use of operator precedence, some abuse of the conditional operator, and a fair bit of *really* dirty macro tricks like including the end of statement termininator within a macro. And that's just getting started; there's plenty more nasties in there!
So, lets say a painter paints a picture. She has a finite palette of colours and brushes. She may extend her palette to infinity with clever mixing of them, although the human eye will not be able to distinguish all of them making it finite from the human perspective. She paints a picture with these tools, according to her skill. Her skill may be self taught, but fundamentals will remain the same, such as perspective and shadowing.
Programmers have a similar toolset. A finite number of commands that may be applied. But the data may be combined into an infinite series of combinations (the limit being memory in the machine). The programmer can then apply code and data into the final work of art.
You may argue that the above is merely skill. I'd argue that in order to appreciate the art of it, you must be skilled yourself. And the last time I saw "proper art" was with an ex girlfriend (who was at art college at the time) I just saw a piece of paper with random flicks of paint that looked like a decorators' dustsheet. She, however, saw juxtaposition, drama and technique, and called it art.
Kill the baddies.
Get the girl.
And save the entire planet.
[ Parent ]