unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Stoeber <paul.stoeber@stud.tu-ilmenau.de>
Subject: Re: segfault after changing max-lisp-eval-depth and max-specpdl-size
Date: Tue, 28 May 2002 23:22:38 +0200	[thread overview]
Message-ID: <20020528212238.GA489593@bruegel.RZ.TU-Ilmenau.DE> (raw)
In-Reply-To: <200205282023.g4SKNoU10649@aztec.santafe.edu>

On Tue, May 28, 2002 at 02:23:50PM -0600, Richard Stallman wrote:
> It is not easy for Emacs to recover from a real stack overflow.
> Part of the reason for these variables is so that it won't get one.

That means I'll have to use let/while/setq instead of recursion
in order to "Avoid arbitrary limits", which produces less
enjoyable code.

I hoped the Lisp interpreter would use my available memory to evaluate
expressions as far as possible, until ENOMEM, instead of bothering me
with oddities like `max-lisp-eval-depth' and `max-specpdl-size'.  But
for that it would need a hand-allocated stack instead of the C stack.
You probably don't want to change the implementation that much.

Emacs Lisp seems to serve its purpose as it is.  It's not a functional
programming language, and it doesn't need to be one.  Forget I ever asked.

  reply	other threads:[~2002-05-28 21:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27 15:53 segfault after changing max-lisp-eval-depth and max-specpdl-size Paul Stoeber
2002-05-28 20:23 ` Richard Stallman
2002-05-28 21:22   ` Paul Stoeber [this message]
2002-05-30 17:05     ` Richard Stallman

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=20020528212238.GA489593@bruegel.RZ.TU-Ilmenau.DE \
    --to=paul.stoeber@stud.tu-ilmenau.de \
    /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).