From: Mike Mattie <codermattie@gmail.com>
To: emacs developers <emacs-devel@gnu.org>
Subject: max-lisp-eval-depth safe upper bounds ?
Date: Tue, 8 Apr 2008 21:30:44 -0700 [thread overview]
Message-ID: <20080408213044.597adc70@reforged> (raw)
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
Hello,
the variable max-lisp-eval-depth as documented can be enlarged significantly but the docs give no safe upper bounds, and
a warning that you can overflow the C stack. What is the safe upper limit for this variable ?
Can the documentation give a safe upper-limit ?
Cheers,
Mike Mattie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2008-04-09 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 4:30 Mike Mattie [this message]
2008-04-09 8:27 ` max-lisp-eval-depth safe upper bounds ? Andreas Schwab
2008-04-09 14:41 ` Lennart Borgman (gmail)
2008-04-09 15:28 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080408213044.597adc70@reforged \
--to=codermattie@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).