diff options
| author | Richard M. Stallman <rms@gnu.org> | 1998-05-19 03:45:57 +0000 |
|---|---|---|
| committer | Richard M. Stallman <rms@gnu.org> | 1998-05-19 03:45:57 +0000 |
| commit | a9f0a989a17f47f9d25b7a426b4e82a8ff684ee4 (patch) | |
| tree | d62b5592064177c684f1509989b223623db3f24c /lispref/macros.texi | |
| parent | c6d6572475603083762cb0155ae966de7710bb9c (diff) | |
| download | emacs-a9f0a989a17f47f9d25b7a426b4e82a8ff684ee4.tar.gz | |
*** empty log message ***
Diffstat (limited to 'lispref/macros.texi')
| -rw-r--r-- | lispref/macros.texi | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/lispref/macros.texi b/lispref/macros.texi index b9e93bcf6d4..0a739bc3ba5 100644 --- a/lispref/macros.texi +++ b/lispref/macros.texi @@ -503,7 +503,7 @@ in expressions ordinarily. @node Eval During Expansion @subsection Evaluating Macro Arguments in Expansion - Another problem can happen if you the macro definition itself + Another problem can happen if the macro definition itself evaluates any of the macro argument expressions, such as by calling @code{eval} (@pxref{Eval}). If the argument is supposed to refer to the user's variables, you may have trouble if the user happens to use a @@ -542,7 +542,7 @@ with @code{eval}) don't occur and its local variable bindings don't exist. To avoid these problems, @strong{don't evaluate an argument expression -while computing the macro expansion.} Instead, substitute the +while computing the macro expansion}. Instead, substitute the expression into the macro expansion, so that its value will be computed as part of executing the expansion. This is how the other examples in this chapter work. |