All the arguments against the CL-style macros are stemming from the fact that it&#x27;s far too easy to get into a total mess with them, simply because of their infinite flexibility. Yet, if you follow some very simple rules, you&#x27;ll get the opposite.<p>Firstly, macros must be simple and must essentially correspond to compiler passes.<p>E.g., if you&#x27;re implementing an embedded DSL for regular expressions, one macro expansion pass should lower your DSL down to a syntax-expanded regular expression, the second macro would lower it into an NFA, another one would construct an optimised DFA, and then the next one (or more) would generate the actual automaton code in Lisp out of the DFA.<p>The best possible case is when your macro pass can be expressed as a set of simple term rewriting rules. And most of the transforms you&#x27;d find in DSL compilers can actually be represented as such.<p>Of course, there is also an alternative style, which may be preferable if you have debugging tools for designing your compiler passes at least equivalent to the Lisp macro expansion debugging. You can simply write your entire DSL compiler as a single function, and then wrap it into a macro, as `(defmacro mydsl (&amp;rest args) (mydsl-compiler args))`.<p>This way, the same compiler infrastructure can be reused for an interpreted or partially interpreted version of your DSL, if you need it. Still, all the same rules apply to how the passes are implemented in that compiler function.<p>Another very useful trick is to make your DSLs composable, which is easy if you split your compilation pipeline into separate macro expansion passes. Multiple DSLs may easily share features of their internal IRs or even front-end languages, so any new DSL would simply cherry-pick features from a number of existing DSLs and wrap them into a simple front-end. This degree of composability is simply impossible with the function-based interpreted eDSLs.<p>A can recommend taking a look at the Nanopass [1] framework, which is built around this very ideology, or at my own DSL construction framework [2].<p>[1] <a href="http:&#x2F;&#x2F;andykeep.com&#x2F;pubs&#x2F;np-preprint.pdf" rel="nofollow">http:&#x2F;&#x2F;andykeep.com&#x2F;pubs&#x2F;np-preprint.pdf</a><p>And some examples:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;cisco&#x2F;ChezScheme" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;cisco&#x2F;ChezScheme</a><p><a href="https:&#x2F;&#x2F;github.com&#x2F;eholk&#x2F;harlan" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;eholk&#x2F;harlan</a><p>[2] <a href="https:&#x2F;&#x2F;github.com&#x2F;combinatorylogic&#x2F;mbase" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;combinatorylogic&#x2F;mbase</a>