> Except, of course, that doesn’t work. The preprocessor 
  > only makes one pass through the file, meaning a macro 
  > can’t call another macro.

  macro.c:
  #include <stdio.h>
  #define LOOP(n) for (int i = 0; i < n; i++)
  #define PRINT10 LOOP(10) { printf("%d", i); }
  int main(void) { PRINT10; printf("\n"); }

  gcc -Wall -std=gnu99 macro.c  && a.out 
  0123456789

Of course macros can call other macros: http://gcc.gnu.org/onlinedocs/cppinternals/Macro-Expansion.h...

Ignoring his poorly protected macros, and taking nothing away from Lisp, am I missing some subtle point he's making, or is the author just flat out wrong here? I think he's just wrong, and this makes it hard for me to even read the rest of his argument.