summaryrefslogtreecommitdiff
path: root/lispref
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>2001-06-23 16:08:32 +0000
committerRichard M. Stallman <rms@gnu.org>2001-06-23 16:08:32 +0000
commit456ced1fb4e1af9b45dad161f57405912fded247 (patch)
tree1cf27aaa63c6ecf5e6e938db9a7c36eca31b8d30 /lispref
parentb9332010d20bd4131aa931cb243a20176c1bda09 (diff)
downloademacs-456ced1fb4e1af9b45dad161f57405912fded247.tar.gz
(Compilation Functions): Add xref to Problems with Macros.
Diffstat (limited to 'lispref')
-rw-r--r--lispref/compile.texi4
1 files changed, 3 insertions, 1 deletions
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