Macrodynamics is a language extension that broadens the notion of dynamic scope inside macroexpansion code. Macrodynamic bindings are scoped not just to the code called during an individual expansion, but also to subsequent expansions of the code returned within the dynamic scope of those bindings.
This goes a long way toward rectifying a major limitation of Common Lisp, described in detail here. In short, you can write macros that behave as if they were expanded recursively instead of iteratively. However, macrodynamics only lets data flow downstream from where it is bound; it does not provide analogues of conditions or continuations to transmit information back up the expansion stack.
You can declare macrodynamic variables with
def-dynenv-var, a cognate of
defvar. These variables can be left unbound or given a top-level, global value.
(def-dynenv-var **my-macrodynamic-var** value) (def-dynenv-var **my-unbound-macrodynamic-var**)
(You may want to use a special notational convention for macrodynamic variables and functions. I prefer
For macrodynamic functions,
def-dynenv-fun works like
def-unbound-dynenv-fun only takes a name which remains unbound at the top-level. (There's just no way to sensibly combine both syntaxes within one macro.)
(def-dynenv-fun **my-macrodynamic-fun** (&rest stuff) (do-stuff-with stuff)) (def-unbound-dynenv-fun **my-unbound-macrodynamic-fun**)
Macrodynamic variables and functions live in a separate namespace from regular Lisp variables (whether lexical or dynamic) and functions. To establish bindings for them, you must use one of a few dynamic-only compile-time variants of familiar operators.
ct-let* bind variables, and
ct-flet binds functions.
Within the body of any function definition created with
ct-flet, the function name
call-next-dynenv-fun is bound (lexically, not dynamically!) to the previously dynamically-bound function with the same name. But any recursive invocation of the function by name, even within a call to
call-next-dynenv-fun, will always invoke the most recently dynamically-bound function. You can also retrieve dynamically-bound functions as values using
dynenv-function instead of
#' simply retrieves a wrapper for calling the dynamically-bound function, which may be rebound between the time you retrieve the wrapper and the time you invoke it. For more details, see Pascal Costanza's paper on dynamically-scoped functions.
To define macros that need to read or bind macrodynamic entities within the dynamic scope of their expander code, you can use
(def-dynenv-var **a-macrodynamic-var** nil) (def-dynenv-macro some-macro (&body body) `(do-stuff ,(do-something) ,(ct-let ((**a-macrodynamic-var** (non-destructively-augment **a-macrodynamic-var**))) `(progn ,@body)))) ;; this function will signal an error if not called within the dynamic scope ;; of a macrodynamic macro's expansion (defun do-something () (generate-code-with **a-macrodynamic-var**)) (defmacro dummy-wrapper-for-some-macro (&body body) `(some-macro ,@body))
Then if you write a form like this:
(some-macro (dummy-wrapper-for-some-macro (some-macro (some-other-code))))
do-something will see the global binding
**a-macrodynamic-var** during the expansion of the top-level
some-macro form, then it will see a new binding equivalent to
(non-destructively-augment nil) in the expansion of the
some-macro form that
dummy-wrapper-for-some-macro's expansion returns, then another new binding equivalent to
(non-destructively-augment (non-destructively-augment nil)) in the innermost
def-dynenv-macro is just a convenience macro that can extract the macrodynamic context from the lexical environment regardless of whether you include an
&environment parameter. (An analogous
dynenv-macrolet macro is also provided.) Alternatively, you can explicitly pass an environment to
with-dynenv at the top of a macro's body (or at least surrounding any forms that need to bind or reference macrodynamic entities). This makes it easier to integrate macrodynamics with any other special macro-defining-macros you might want to use.
(def-macro-using-some-other-macro-library some-macro (&body body &environment env) (with-dynenv env `(do-stuff ,(do-something) ,(ct-let ((**a-macrodynamic-var** (non-destructively-augment **a-macrodynamic-var**))) (remember-that-you-can-also-see-the-new-value-of **a-macrodynamic-var** immediately-right-here-in-the-same-expansion-step! `(progn ,@body))))))
This library is meant to be used in a purely functional manner, and it will signal an error if you attempt to set, rather than rebind, a macrodynamic binding. That's right, dynamic scope is compatible with functional programming; it just admits a slightly looser definition of referential transparency. You can think of dynamic variables as an implicit set of additional arguments passed to every function. When dynamic bindings are in play, a function called with the same arguments may not always return the same results, but a function called at the top-level with the same arguments always will. What this means for macrodynamics is that an entire top-level form will always have the same macroexpansion. Normally, this is all you really care about, since you spend most of your time reasoning about top-level forms that you can see in their entirety.
One drawback is that you won't always be able to use SLIME's
C-c C-m to verify what a non-top-level expression will expand into, but this is no different from any other situation in which you might use
symbol-macrolet. Macrodynamics are no more dangerous than lexically-bound macros; in fact, they're just an abstraction layer built on top of
What is dynamic from the perspective of expander code is lexical from the perspective of expanded code. When you take full advantage of this semantic duality, it's easy to lexically scope, and thus make more composable, certain implementation concerns that do not easily map onto lexical runtime variables. In the most common case, you can bind compile-time metadata about how a given variable is meant to be interpreted by another macro that may or may not be used further down the syntax tree.
Instead of placing your trust in a code walker like macroexpand-dammit, macrodynamics piggybacks on your implementation's built-in macroexpansion facility. When you use a code walker, you introduce a potential point of failure that can screw up the expansion of code in between the macro that establishes a compile-time dynamic context and the macro that uses it. With macrodynamics, you can trust your Lisp implementation to correctly process any in-between special operators, function calls, and macros that were written without any knowledge of this language extension.
- Kyle Littler