Bastien <bzg <at> altern.org> writes: > One potential problem in the first test is the use of "parent" as the > name of the symbol to pass to the macro... since this is the very same > name than the macro second argument. At least this reminded me this > section of Elisp manual:
I've actually tested this by renaming the macro arguments and no symbol capturing seems to be involved via this path. The symbol is never used unquoted in the macro expansion anyway. > So... instead of fixing the macro calls in the tests, I've been > wondering why using a macro for `org-export-define-derived-backend' > and `org-export-define-backend' would be better? I think that these are proper uses of macros since Nicolas is introducing special syntax for defining a backend. In any case before anything is changed we should know why this is happening at all. Regards, Achim.
