diff options
| author | Richard M. Stallman | 2007-11-25 03:49:34 +0000 |
|---|---|---|
| committer | Richard M. Stallman | 2007-11-25 03:49:34 +0000 |
| commit | cc060ff7916412eeebe3dc52adad8e4417708630 (patch) | |
| tree | adbcdb44c0d98081551b65b99356ee45bf62b94e | |
| parent | fc99733207e6a894a2067a7b832c126f859dc865 (diff) | |
| download | emacs-cc060ff7916412eeebe3dc52adad8e4417708630.tar.gz emacs-cc060ff7916412eeebe3dc52adad8e4417708630.zip | |
(Eval During Expansion): Minor cleanup.
| -rw-r--r-- | doc/lispref/macros.texi | 2 |
1 files changed, 1 insertions, 1 deletions
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: | |||
| 623 | 623 | ||
| 624 | Another problem with calling @code{eval} in a macro definition is that | 624 | Another problem with calling @code{eval} in a macro definition is that |
| 625 | it probably won't do what you intend in a compiled program. The | 625 | it probably won't do what you intend in a compiled program. The |
| 626 | byte-compiler runs macro definitions while compiling the program, when | 626 | byte compiler runs macro definitions while compiling the program, when |
| 627 | the program's own computations (which you might have wished to access | 627 | the program's own computations (which you might have wished to access |
| 628 | with @code{eval}) don't occur and its local variable bindings don't | 628 | with @code{eval}) don't occur and its local variable bindings don't |
| 629 | exist. | 629 | exist. |