[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/lispref/edebug.texi
From: |
Richard M. Stallman |
Subject: |
[Emacs-diffs] Changes to emacs/lispref/edebug.texi |
Date: |
Tue, 05 Aug 2003 21:25:23 -0400 |
Index: emacs/lispref/edebug.texi
diff -c emacs/lispref/edebug.texi:1.16 emacs/lispref/edebug.texi:1.17
*** emacs/lispref/edebug.texi:1.16 Tue Jun 24 14:15:06 2003
--- emacs/lispref/edebug.texi Tue Aug 5 21:25:23 2003
***************
*** 1077,1091 ****
...)
@end example
! @defspec declare (edebug @var{specification})
! Specify which expressions of a call to the macro in which the
! declaration appears are forms to be evaluated. For simple macros, the
! @var{specification} often looks very similar to the formal argument list
! of the macro definition, but specifications are much more general than
! macro arguments.
! @end defspec
! You can also define an edebug specification for a macro separately
from the macro definition with @code{def-edebug-spec}. Adding
@code{edebug} declarations is preferred, and more convenient, for
macro definitions in Lisp, but @code{def-edebug-spec} makes it
--- 1077,1090 ----
...)
@end example
! The Edebug specifation says which parts of a call to the macro are
! forms to be evaluated. For simple macros, the @var{specification}
! often looks very similar to the formal argument list of the macro
! definition, but specifications are much more general than macro
! arguments. @xref{Defining Macros}, for more explanation of
! the @code{declare} special form.
! You can also define an edebug specification for a macro separately
from the macro definition with @code{def-edebug-spec}. Adding
@code{edebug} declarations is preferred, and more convenient, for
macro definitions in Lisp, but @code{def-edebug-spec} makes it
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] Changes to emacs/lispref/edebug.texi,
Richard M. Stallman <=