> Now you discover that the problem is in a macro written in another module.
> Changing that affects other uses as well.. so you need to write an new one
> when you
> have figured out what this guy was trying to do in the first place.
Or for a one off problem, you could macroexpand-1 the statement and
then patch it, leave the original in place as a comment, and, if it
wasn't simple misuse of the macro, put a note next to the macro
definition pointing to this fix.
Your solution is the same as rewriting a major library the first time
you have problems calling it.