aboutsummaryrefslogtreecommitdiffstats
path: root/doc/lispref/eval.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/lispref/eval.texi')
-rw-r--r--doc/lispref/eval.texi5
1 files changed, 1 insertions, 4 deletions
diff --git a/doc/lispref/eval.texi b/doc/lispref/eval.texi
index 6e29a5403f1..11c321b32ed 100644
--- a/doc/lispref/eval.texi
+++ b/doc/lispref/eval.texi
@@ -830,7 +830,7 @@ This variable defines the maximum depth allowed in calls to @code{eval},
830@code{apply}, and @code{funcall} before an error is signaled (with error 830@code{apply}, and @code{funcall} before an error is signaled (with error
831message @code{"Lisp nesting exceeds max-lisp-eval-depth"}). 831message @code{"Lisp nesting exceeds max-lisp-eval-depth"}).
832 832
833This limit, with the associated error when it is exceeded, is one way 833This limit, with the associated error when it is exceeded, is how
834Emacs Lisp avoids infinite recursion on an ill-defined function. If 834Emacs Lisp avoids infinite recursion on an ill-defined function. If
835you increase the value of @code{max-lisp-eval-depth} too much, such 835you increase the value of @code{max-lisp-eval-depth} too much, such
836code can cause stack overflow instead. On some systems, this overflow 836code can cause stack overflow instead. On some systems, this overflow
@@ -851,9 +851,6 @@ less than 100, Lisp will reset it to 100 if the given value is
851reached. Entry to the Lisp debugger increases the value, if there is 851reached. Entry to the Lisp debugger increases the value, if there is
852little room left, to make sure the debugger itself has room to 852little room left, to make sure the debugger itself has room to
853execute. 853execute.
854
855@code{max-specpdl-size} provides another limit on nesting.
856@xref{Definition of max-specpdl-size,, Local Variables}.
857@end defopt 854@end defopt
858 855
859@defvar values 856@defvar values