>>75Actually i've been posting the whole week. I just wanted to show this "Advanced LISP wizardry"(which Paul Graham is fond of) is equivalent to "primitive, text juggling" C preprocessor macro.
The "killer feature" is passing code to the macro to expand somewhere and integrate into the macro. e.g. textreplace(parametername, chunkofcode) you can pass entire programs as ({macroblocks}) in C and even chain them in like 10 levels of macroexpansion. Nobody even thinks these are killer features, they are basic abstractions.
Example:
#define macropgrogram3(arg1,...) ({;arg1+1;})
#define macro3(macroprogram1,macroprogram2,macroprogram3,...) macroprogram1(macroprogram2(macroprogram3(__VA_ARGS__)))
Advanced LISP wizards would claim this macro chain is "function combinator" "lambda calculus" or some kind of academic bullshit which is only available in their LISP/Haskell/academic language.
Also, i see like 90% of TOR exit nodes blocked and this makes it harder to post.