From e21f0189f3fab8264e05c26056324e878f166c1c Mon Sep 17 00:00:00 2001 From: Noam Postavsky Date: Tue, 30 Jan 2018 23:02:05 -0500 Subject: [PATCH] * doc/lispref/functions.texi (Inline Functions): Fix typo (Bug#30238). --- doc/lispref/functions.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi index 277a42d2c2f..b53d1f0bb90 100644 --- a/doc/lispref/functions.texi +++ b/doc/lispref/functions.texi @@ -2093,7 +2093,7 @@ to verify that using @code{defun} actually has performance problems. After an inline function is defined, its inline expansion can be performed later on in the same file, just like macros. - It's possible to use @code{defsubst} to define a macro to expand + It's possible to use @code{defmacro} to define a macro to expand into the same code that an inline function would execute (@pxref{Macros}). But the macro would be limited to direct use in expressions---a macro cannot be called with @code{apply}, -- 2.39.2