# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1060133123 0
# Node ID 187f0047b980990ef2513bdeac2b626c55ccb8d5
# Parent  a5d4d0a7b28462137c129664442ea0520a1e3b52
(Instrumenting Macro Calls): Don't define `declare' here;
instead xref Defining Macros.

diff -r a5d4d0a7b284 -r 187f0047b980 lispref/edebug.texi
--- a/lispref/edebug.texi	Wed Aug 06 01:23:14 2003 +0000
+++ b/lispref/edebug.texi	Wed Aug 06 01:25:23 2003 +0000
@@ -1077,15 +1077,14 @@
   ...)
 @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
+  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
+  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