On 1 Sep 2010, at 08:25, Konrad Hinsen wrote:
Right, but then this should be blamed on macroexpand-all, which
implements a crude approximation to how macroexpansion is done by
the compiler.
There's also clojure.contrib.macro-utils/mexpand-all, which does a
much better job, but still fails for this particular example. In
fact, neither one tracks the lexical environment.
clojure.contrib.macro-utils/mexpand-all now does track the lexical
environment. In fact, it already did before, but it used that
information only for symbol macro expansion.
Konrad.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
