Stefan Monnier writes: > I don't know what to do when a macro calls it (I can't think of any > reason we'd want to do that), but I know how to handle the case where > a macro outputs code that uses it: Add (byte-defop-compiler-1 > function-put) as well as a byte-compile-function-put function. > See byte-compile-autoload and byte-compile-make-obsolete-variable > for examples. Oh, I think I get it now.