From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Paul Stoeber Newsgroups: gmane.emacs.bugs Subject: Re: segfault after changing max-lisp-eval-depth and max-specpdl-size Date: Tue, 28 May 2002 23:22:38 +0200 Sender: bug-gnu-emacs-admin@gnu.org Message-ID: <20020528212238.GA489593@bruegel.RZ.TU-Ilmenau.DE> References: <20020527155352.GA454374@bruegel.RZ.TU-Ilmenau.DE> <200205282023.g4SKNoU10649@aztec.santafe.edu> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1022621026 489 127.0.0.1 (28 May 2002 21:23:46 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 28 May 2002 21:23:46 +0000 (UTC) Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17CoRV-00007m-00 for ; Tue, 28 May 2002 23:23:46 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17CoSD-0003cb-00; Tue, 28 May 2002 17:24:29 -0400 Original-Received: from bruegel.rz.tu-ilmenau.de ([141.24.190.37]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17CoPz-0003Wx-00 for ; Tue, 28 May 2002 17:22:11 -0400 Original-Received: (from past-in@localhost) by bruegel.rz.tu-ilmenau.de (SGI-8.9.3/8.9.3) id XAA88283 for bug-gnu-emacs@gnu.org; Tue, 28 May 2002 23:22:38 +0200 (MDT) Original-To: bug-gnu-emacs@gnu.org Content-Disposition: inline In-Reply-To: <200205282023.g4SKNoU10649@aztec.santafe.edu> User-Agent: Mutt/1.3.28i Errors-To: bug-gnu-emacs-admin@gnu.org X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.bugs:1653 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:1653 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.