From: Richard M. Stallman <rms@gnu.org>
Date: Wed, 6 Aug 2003 01:25:23 +0000 (+0000)
Subject: (Instrumenting Macro Calls): Don't define `declare' here;
X-Git-Tag: ttn-vms-21-2-B4~9154
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=a756468d977f42ea99130622b9472374309ee1dd;p=emacs.git

(Instrumenting Macro Calls): Don't define `declare' here;
instead xref Defining Macros.
---

diff --git a/lispref/edebug.texi b/lispref/edebug.texi
index 8ddbcf7a74f..fd7f1175ed0 100644
--- a/lispref/edebug.texi
+++ b/lispref/edebug.texi
@@ -1077,15 +1077,14 @@ For example, (for i from 1 to 10 do (print i))."
   ...)
 @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
+  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