That's an excellent interview question. Particularly for any experienced programmer who puts MACRO on their resume. It would (could) start an interesting discussion about the costs and benefits of code generation, modularization, etc.
Too many people learn the macro language too soon, and over-use it seeing every problem as having a macro solution. Or maybe over-use of macro is just a natural step on the learning curve. When you understand *when* it's appropriate to use macro, and can explain *why* in your judgement macro is appropriate in those contexts, then you're an experienced macro user.
It's not surprising to me that there will be as many different answers to the question as there are programmers. Lots of folks hate the macro language, or see it as something of limited use which should be avoided as much as possible. Even among macro enthusiasts, we differ dramatically on our thoughts on the appropriateness of things like :
autocall libraries
permanent compiled macro libraries
macros with no parameters
macros with no macro code (i.e. using macros solely for modularlzation, like %include)
global macro variables
function-style macros
etc etc etc
... View more