From 6fbf37a575e34a2313dfff059862a973c7bf512b Mon Sep 17 00:00:00 2001 From: Lars Ingebrigtsen <larsi@gnus.org> Date: Wed, 2 Feb 2022 19:55:19 +0100 Subject: [PATCH] Add some indexing for "compiler macro" * doc/lispref/functions.texi (Inline Functions): Add a link to where compiler macros are defined. (Declare Form): Add a concept index. --- doc/lispref/functions.texi | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi index 2378e9efd7e..207919ea645 100644 --- a/doc/lispref/functions.texi +++ b/doc/lispref/functions.texi @@ -2153,8 +2153,8 @@ worry about how many times the body uses the arguments, as you do for macros. Alternatively, you can define a function by providing the code which -will inline it as a compiler macro. The following macros make this -possible. +will inline it as a compiler macro (@pxref{Declare Form}). The +following macros make this possible. @c FIXME: Can define-inline use the interactive spec? @defmac define-inline name args [doc] [declare] body@dots{} @@ -2310,6 +2310,7 @@ which case the warning message gives no extra details). @var{when} should be a string indicating when the function or macro was first made obsolete. +@cindex compiler macro @item (compiler-macro @var{expander}) This can only be used for functions, and tells the compiler to use @var{expander} as an optimization function. When encountering a call to the -- 2.39.5