HCoop
/
bpt
/
emacs.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
*** empty log message ***
[bpt/emacs.git]
/
lispref
/
macros.texi
diff --git
a/lispref/macros.texi
b/lispref/macros.texi
index
b940125
..
80d8e9c
100644
(file)
--- a/
lispref/macros.texi
+++ b/
lispref/macros.texi
@@
-1,6
+1,7
@@
@c -*-texinfo-*-
@c This is part of the GNU Emacs Lisp Reference Manual.
@c -*-texinfo-*-
@c This is part of the GNU Emacs Lisp Reference Manual.
-@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 2004 Free Software Foundation, Inc.
+@c Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995, 1998, 2001, 2002,
+@c 2003, 2004, 2005, 2006, 2007 Free Software Foundation, Inc.
@c See the file elisp.texi for copying conditions.
@setfilename ../info/macros
@node Macros, Customization, Functions, Top
@c See the file elisp.texi for copying conditions.
@setfilename ../info/macros
@node Macros, Customization, Functions, Top
@@
-140,13
+141,10
@@
uses this feature.
@defun macroexpand-all form &optional environment
@cindex macro expansion in entire form
@defun macroexpand-all form &optional environment
@cindex macro expansion in entire form
-
@code{macroexpand-all} expands macros like @code{macroexpand}, but
will look for and expand all macros in @var{form}, not just at the
@code{macroexpand-all} expands macros like @code{macroexpand}, but
will look for and expand all macros in @var{form}, not just at the
-top-level.
-
-In emacs-lisp, @code{macroexpand-all} guarantees that if no macros
-are expanded, the return value will be @code{eq} to @var{form}.
+top-level. If no macros are expanded, the return value is @code{eq}
+to @var{form}.
Repeating the example used for @code{macroexpand} above with
@code{macroexpand-all}, we see that @code{macroexpand-all} @emph{does}
Repeating the example used for @code{macroexpand} above with
@code{macroexpand-all}, we see that @code{macroexpand-all} @emph{does}
@@
-232,14
+230,14
@@
called interactively.
which can specify how @key{TAB} should indent macro calls, and how to
step through them for Edebug.
which can specify how @key{TAB} should indent macro calls, and how to
step through them for Edebug.
-@anchor{Definition of declare}
@defmac declare @var{specs}@dots{}
@defmac declare @var{specs}@dots{}
+@anchor{Definition of declare}
A @code{declare} form is used in a macro definition to specify various
additional information about it. Two kinds of specification are
currently supported:
@table @code
A @code{declare} form is used in a macro definition to specify various
additional information about it. Two kinds of specification are
currently supported:
@table @code
-@item (
e
debug @var{edebug-form-spec})
+@item (debug @var{edebug-form-spec})
Specify how to step through macro calls for Edebug.
@xref{Instrumenting Macro Calls}, for more details.
Specify how to step through macro calls for Edebug.
@xref{Instrumenting Macro Calls}, for more details.
@@
-448,7
+446,7
@@
For example, (for i from 1 to 10 do (print i))."
(let ((i 1))
(while (<= i 3)
(setq square (* i i))
(let ((i 1))
(while (<= i 3)
(setq square (* i i))
- (princ (format "
%d
%d" i square))
+ (princ (format "
\n%d
%d" i square))
(inc i)))
@end group
@group
(inc i)))
@end group
@group
@@
-715,7
+713,7
@@
This is the same as no property---use the standard indentation pattern.
@item @code{defun}
Handle this function like a @samp{def} construct: treat the second
line as the start of a @dfn{body}.
@item @code{defun}
Handle this function like a @samp{def} construct: treat the second
line as the start of a @dfn{body}.
-@item a
numb
er, @var{number}
+@item a
n integ
er, @var{number}
The first @var{number} arguments of the function are
@dfn{distinguished} arguments; the rest are considered the body
of the expression. A line in the expression is indented according to
The first @var{number} arguments of the function are
@dfn{distinguished} arguments; the rest are considered the body
of the expression. A line in the expression is indented according to