summaryrefslogtreecommitdiff
path: root/doc/lispref/macros.texi
diff options
context:
space:
mode:
authorGlenn Morris <rgm@gnu.org>2012-11-17 17:38:42 -0800
committerGlenn Morris <rgm@gnu.org>2012-11-17 17:38:42 -0800
commit7351b73d45a2f6f33230e6725fdfdf9e122eff14 (patch)
tree2e6153d48902f57bc279fce27736e484d537823e /doc/lispref/macros.texi
parent7f6705c313ce5054fdcbc457fa32b9680bcb11a7 (diff)
downloademacs-7351b73d45a2f6f33230e6725fdfdf9e122eff14.tar.gz
Document eager macro expansion
* doc/lispref/loading.texi (How Programs Do Loading): Add eager macro expansion. * doc/lispref/macros.texi (Expansion): Mention eager macro expansion. * etc/NEWS: Related edit.
Diffstat (limited to 'doc/lispref/macros.texi')
-rw-r--r--doc/lispref/macros.texi4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/lispref/macros.texi b/doc/lispref/macros.texi
index 8be6a3fbcde..b0dee1bf215 100644
--- a/doc/lispref/macros.texi
+++ b/doc/lispref/macros.texi
@@ -86,6 +86,10 @@ macro.
calls to other macros. It may even be a call to the same macro, though
this is unusual.
+ Note that Emacs tries to expand macros when loading an uncompiled
+Lisp file. This is not always possible, but if it is, it speeds up
+subsequent execution. @xref{How Programs Do Loading}.
+
You can see the expansion of a given macro call by calling
@code{macroexpand}.