summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStefan Monnier <monnier@iro.umontreal.ca>2022-09-28 14:14:32 -0400
committerStefan Monnier <monnier@iro.umontreal.ca>2022-09-28 14:14:32 -0400
commitb6a163ba7cdf57eff5542b4cb6956780ebb2880f (patch)
treea2c3b7378c0f289515978d23cff9ca16a450a956
parent1254d9a3ae89697b591343de2ddf55c5879bc937 (diff)
downloademacs-b6a163ba7cdf57eff5542b4cb6956780ebb2880f.tar.gz
* doc/lispref/functions.texi (Declare Form) <compiler-macro>: Re-rephrase
-rw-r--r--doc/lispref/functions.texi7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
index 0659d3556bb..8b858e0aa01 100644
--- a/doc/lispref/functions.texi
+++ b/doc/lispref/functions.texi
@@ -2478,9 +2478,10 @@ expander will call @var{expander} with that form as well as with
instead of the function call, or it can return just the form unchanged,
to indicate that the function call should be left alone.
-When @var{expander} is a lambda form it should be of the form
-@code{(lambda (@var{arg}) @var{body})} because the function's formal
-arguments are automatically added to the lambda's list of arguments.
+When @var{expander} is a lambda form it should be written with
+a single argument (i.e., be of the form @code{(lambda (@var{arg})
+@var{body})}) because the function's formal arguments are
+automatically added to the lambda's list of arguments for you.
@item (gv-expander @var{expander})
Declare @var{expander} to be the function to handle calls to the macro (or