From 456ced1fb4e1af9b45dad161f57405912fded247 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Sat, 23 Jun 2001 16:08:32 +0000 Subject: [PATCH] (Compilation Functions): Add xref to Problems with Macros. --- lispref/compile.texi | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/lispref/compile.texi b/lispref/compile.texi index 001466d500d..b854fc86edf 100644 --- a/lispref/compile.texi +++ b/lispref/compile.texi @@ -110,7 +110,9 @@ program that suggest a problem but are not necessarily erroneous. Be careful when writing macro calls in files that you may someday byte-compile. Macro calls are expanded when they are compiled, so the macros must already be defined for proper compilation. For more -details, see @ref{Compiling Macros}. +details, see @ref{Compiling Macros}. If a program does not work the +same way when compiled as it does when interpreted, erroneous macro +definitions are one likely cause (@pxref{Problems with Macros}). Normally, compiling a file does not evaluate the file's contents or load the file. But it does execute any @code{require} calls at top -- 2.39.5