# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1085263186 0
# Node ID 93c897de789867a99de7df7ed2c3876258fdfdb6
# Parent  8b5d63bbe285cd629b2b3e80c9f04afdcdb448d6
(Eval): Increasing max-lisp-eval-depth can cause real stack overflow.

diff -r 8b5d63bbe285 -r 93c897de7898 lispref/eval.texi
--- a/lispref/eval.texi	Sat May 22 21:58:24 2004 +0000
+++ b/lispref/eval.texi	Sat May 22 21:59:46 2004 +0000
@@ -678,9 +678,12 @@
 @defvar max-lisp-eval-depth
 This variable defines the maximum depth allowed in calls to @code{eval},
 @code{apply}, and @code{funcall} before an error is signaled (with error
-message @code{"Lisp nesting exceeds max-lisp-eval-depth"}).  This limit,
-with the associated error when it is exceeded, is one way that Lisp
-avoids infinite recursion on an ill-defined function.
+message @code{"Lisp nesting exceeds max-lisp-eval-depth"}).
+
+This limit, with the associated error when it is exceeded, is one way
+Emacs Lisp avoids infinite recursion on an ill-defined function.  If
+you increase the value of @code{max-lisp-eval-depth} too much, such
+code can cause stack overflow instead.
 @cindex Lisp nesting error
 
 The depth limit counts internal uses of @code{eval}, @code{apply}, and