From cc060ff7916412eeebe3dc52adad8e4417708630 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Sun, 25 Nov 2007 03:49:34 +0000 Subject: [PATCH] (Eval During Expansion): Minor cleanup. --- doc/lispref/macros.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/lispref/macros.texi b/doc/lispref/macros.texi index 152b7b652b6..81477bb2eff 100644 --- a/doc/lispref/macros.texi +++ b/doc/lispref/macros.texi @@ -623,7 +623,7 @@ it. Here is an example: Another problem with calling @code{eval} in a macro definition is that it probably won't do what you intend in a compiled program. The -byte-compiler runs macro definitions while compiling the program, when +byte compiler runs macro definitions while compiling the program, when the program's own computations (which you might have wished to access with @code{eval}) don't occur and its local variable bindings don't exist. -- 2.39.2