From 4469ed01745ff544677656f3c23b3a38e9c0d7f7 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Wed, 7 Jun 2006 17:53:03 +0000 Subject: [PATCH] (Eval During Compile): Fix a typo. Add index entries for possible uses of eval-when-compile. --- lispref/compile.texi | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/lispref/compile.texi b/lispref/compile.texi index 4b796697731..1b18e0ee284 100644 --- a/lispref/compile.texi +++ b/lispref/compile.texi @@ -435,15 +435,16 @@ compiler becomes a constant which appears in the compiled program. If you load the source file, rather than compiling it, @var{body} is evaluated normally. +@cindex compile-time constant If you have a constant that needs some calculation to produce, -@code{eval-when-compile} can do that done at compile-time. For -example, +@code{eval-when-compile} can do that at compile-time. For example, @lisp (defvar my-regexp (eval-when-compile (regexp-opt '("aaa" "aba" "abb")))) @end lisp +@cindex macros, at compile time If you're using another package, but only need macros from it (the byte compiler will expand those), then @code{eval-when-compile} can be used to load it for compiling, but not executing. For example, -- 2.39.5