A Macro to Unravel Macros
Sarah J. Woodruff · 2009
Do you find it tedious to pinpoint problems in your macro code? Are you annoyed when the log points to the line number of the macro call rather than the code in the macro that generated the error? Would you like a little help? You want to produce macros that are utilitarian black boxes, but you need to understand what the code is actually doing as part of the development process, and that can be frustrating. This paper presents a simple wrapper macro that is used to enclose existing code, which can call any number of other macros. When you use this technique along with the mPrint and mFile options, the output file produced by mPrint/mFile contains a completely “de-macroed” version of the program. You can then examine this output as a working program, thus making it easier to both understand and edit.