Mercurial > emacs
comparison lispref/eval.texi @ 55734:93c897de7898
(Eval): Increasing max-lisp-eval-depth can cause real stack overflow.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Sat, 22 May 2004 21:59:46 +0000 |
parents | 22b1822fac7f |
children | c9aa4127a482 4c90ffeb71c5 |
comparison
equal
deleted
inserted
replaced
55733:8b5d63bbe285 | 55734:93c897de7898 |
---|---|
676 | 676 |
677 @anchor{Definition of max-lisp-eval-depth} | 677 @anchor{Definition of max-lisp-eval-depth} |
678 @defvar max-lisp-eval-depth | 678 @defvar max-lisp-eval-depth |
679 This variable defines the maximum depth allowed in calls to @code{eval}, | 679 This variable defines the maximum depth allowed in calls to @code{eval}, |
680 @code{apply}, and @code{funcall} before an error is signaled (with error | 680 @code{apply}, and @code{funcall} before an error is signaled (with error |
681 message @code{"Lisp nesting exceeds max-lisp-eval-depth"}). This limit, | 681 message @code{"Lisp nesting exceeds max-lisp-eval-depth"}). |
682 with the associated error when it is exceeded, is one way that Lisp | 682 |
683 avoids infinite recursion on an ill-defined function. | 683 This limit, with the associated error when it is exceeded, is one way |
684 Emacs Lisp avoids infinite recursion on an ill-defined function. If | |
685 you increase the value of @code{max-lisp-eval-depth} too much, such | |
686 code can cause stack overflow instead. | |
684 @cindex Lisp nesting error | 687 @cindex Lisp nesting error |
685 | 688 |
686 The depth limit counts internal uses of @code{eval}, @code{apply}, and | 689 The depth limit counts internal uses of @code{eval}, @code{apply}, and |
687 @code{funcall}, such as for calling the functions mentioned in Lisp | 690 @code{funcall}, such as for calling the functions mentioned in Lisp |
688 expressions, and recursive evaluation of function call arguments and | 691 expressions, and recursive evaluation of function call arguments and |