Someone who's used macros before extensively— Macros are only unreadable if they're written that way. See, while C can be confusing, it's built using simple to

Someone who's used macros before extensively— Macros are only unreadable if they're written that way. See, while C can be confusing, it's built using simple tools—you can use the c preprocessor apart from the compiler itself. By default, c without cpp is not pre-processed, so you have entire control of the output. (many OS's cc/libc implementations make extensive use of macros, e.g. assert, hence my "default" qualification). Writing with this in mind would allow two layers of compilation—once to verify the pre-processor, once to verify the resulting c compilation. While it is annoying, it doesn't require any more skill than a write-compile-debug loop.