diff options
author | Chong Yidong <cyd@stupidchicken.com> | 2009-03-10 00:43:20 +0000 |
---|---|---|
committer | Chong Yidong <cyd@stupidchicken.com> | 2009-03-10 00:43:20 +0000 |
commit | ebfbce679377b4ead34b24df1a918f7cd17e5974 (patch) | |
tree | 7c899c21cf43a3439e45d48caa676747ff054d98 /doc | |
parent | 955964d7e985c44d107ea1fa7fecc0082f1b02ac (diff) | |
download | emacs-ebfbce679377b4ead34b24df1a918f7cd17e5974.tar.gz |
(Compiling Macros): Omit misleading sentence, which implied that
macros can only be used in the same file they are defined.
(Backquote): Remove obsolete information about Emacs 19.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/lispref/macros.texi | 28 |
1 files changed, 7 insertions, 21 deletions
diff --git a/doc/lispref/macros.texi b/doc/lispref/macros.texi index a78f8c16f1d..935dc6553dc 100644 --- a/doc/lispref/macros.texi +++ b/doc/lispref/macros.texi @@ -178,16 +178,13 @@ itself---they would be computed at compile time, which is not useful. already be defined in Lisp when the calls to them are compiled. The compiler has a special feature to help you do this: if a file being compiled contains a @code{defmacro} form, the macro is defined -temporarily for the rest of the compilation of that file. To make this -feature work, you must put the @code{defmacro} in the same file where it -is used, and before its first use. - - Byte-compiling a file executes any @code{require} calls at top-level -in the file. This is in case the file needs the required packages for -proper compilation. One way to ensure that necessary macro definitions -are available during compilation is to require the files that define -them (@pxref{Named Features}). To avoid loading the macro definition files -when someone @emph{runs} the compiled program, write +temporarily for the rest of the compilation of that file. + + Byte-compiling a file also executes any @code{require} calls at +top-level in the file, so you can ensure that necessary macro +definitions are available during compilation by requiring the files +that define them (@pxref{Named Features}). To avoid loading the macro +definition files when someone @emph{runs} the compiled program, write @code{eval-when-compile} around the @code{require} calls (@pxref{Eval During Compile}). @@ -356,17 +353,6 @@ Here are some examples: @end group @end example -In old Emacs versions, before version 19.29, @samp{`} used a different -syntax which required an extra level of parentheses around the entire -backquote construct. Likewise, each @samp{,} or @samp{,@@} substitution -required an extra level of parentheses surrounding both the @samp{,} or -@samp{,@@} and the following expression. The old syntax required -whitespace between the @samp{`}, @samp{,} or @samp{,@@} and the -following expression. - -This syntax is still accepted, for compatibility with old Emacs -versions, but support for it will be removed in the future. - @node Problems with Macros @section Common Problems Using Macros |