[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] emacs/doc/lispref macros.texi
From: |
Chong Yidong |
Subject: |
[Emacs-diffs] emacs/doc/lispref macros.texi |
Date: |
Tue, 10 Mar 2009 00:43:21 +0000 |
CVSROOT: /sources/emacs
Module name: emacs
Changes by: Chong Yidong <cyd> 09/03/10 00:43:21
Modified files:
doc/lispref : macros.texi
Log message:
(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.
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/emacs/doc/lispref/macros.texi?cvsroot=emacs&r1=1.6&r2=1.7
Patches:
Index: macros.texi
===================================================================
RCS file: /sources/emacs/emacs/doc/lispref/macros.texi,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- macros.texi 8 Jan 2009 05:29:00 -0000 1.6
+++ macros.texi 10 Mar 2009 00:43:20 -0000 1.7
@@ -178,16 +178,13 @@
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 @@
@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
address@hidden,@@} 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] emacs/doc/lispref macros.texi,
Chong Yidong <=