Re: Why is FUNC in cl-callf not allowed to be an expression?

[Michael Heerdegen]

Stefan Monnier <address@hidden> writes:

> > Can we say that macros are "expanded in the global environment", or
>
> Sounds good.

Ok, I installed this:

From 997ac9f829059bf37c81fd586910c834394951e6 Mon Sep 17 00:00:00 2001
From: Michael Heerdegen <address@hidden>
Date: Thu, 23 May 2019 03:33:04 +0200
Subject: [PATCH] * doc/misc/cl.texi (Macro Bindings): Add a detail

Say that calls of 'cl-macrolet' bound macros are expanded in the
global environment.
---
 doc/misc/cl.texi | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/misc/cl.texi b/doc/misc/cl.texi
index eb06791ba9..ee73c65b78 100644
--- a/doc/misc/cl.texi
+++ b/doc/misc/cl.texi
@@ -1359,7 +1359,8 @@ Macro Bindings
 scoped.  The @code{cl-macrolet} binding will
 affect only calls that appear physically within the body
 @var{forms}, possibly after expansion of other macros in the
-body.
+body.  Calls of @code{cl-macrolet} bound macros are expanded in the
+global environment.
 @end defmac

 @defmac cl-symbol-macrolet (address@hidden) address@hidden
--
2.20.1

> A separate @node about when macro expansion can take place and what
> environment it can rely on would be welcome.

That would be good, yes, though, I will probably not be the one writing
it.


Thanks,

Michael.