all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
	Hongyi Zhao <hongyi.zhao@gmail.com>
Subject: Re: `max-specpdl-size' and `max-lisp-eval-depth'
Date: Tue, 28 Sep 2021 13:23:02 +0200	[thread overview]
Message-ID: <87fstpt04p.fsf@gmx.net> (raw)
In-Reply-To: <877df1dk9p.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 28 Sep 2021 13:14:42 +0200")

On Tue, 28 Sep 2021 13:14:42 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> The term goes back to the beginnings of Lisp (McCarthy's paper from
>> 1960, available via the Wayback Machine from
>> http://www-formal.stanford.edu/jmc/recursive/node4.html):
>>
>>   In general (we shall discuss an exception), the routine for a
>>   recursive function uses itself as a subroutine [...] This possible
>>   conflict is resolved by the SAVE and UNSAVE routines that use the
>>   public push-down list.
>
> Perhaps we should put something about this in the `max-specpdl-size' doc
> string.  You wouldn't happen to know what the "spec" part is referring
> to?  :-)

I think that's from the Common Lisp term "special variable" for a global
(i.e. non-lexical) variable.  I don't know where that term originated,
maybe Maclisp.

Steve Berman



  reply	other threads:[~2021-09-28 11:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26  1:48 `max-specpdl-size' and `max-lisp-eval-depth' Hongyi Zhao
2021-09-26  2:36 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-26  6:33   ` Hongyi Zhao
2021-09-26  7:13     ` tomas
2021-09-26 11:26       ` Hongyi Zhao
2021-09-26 11:55         ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-26 13:04         ` Eli Zaretskii
2021-09-26 15:01           ` Hongyi Zhao
2021-09-28 10:50             ` Stephen Berman
2021-09-28 11:03               ` Hongyi Zhao
2021-09-28 11:05               ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-28 11:20                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-28 13:49                 ` tomas
2021-09-28 14:08                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-28 14:19                     ` tomas
2021-09-28 11:14               ` Lars Ingebrigtsen
2021-09-28 11:23                 ` Stephen Berman [this message]
2021-09-29  5:53                   ` Lars Ingebrigtsen
2021-09-26  3:53 ` [External] : " Drew Adams
2021-09-26  4:09   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-28  3:45     ` Google vi (was: Re: [External] : `max-specpdl-size' and `max-lisp-eval-depth') Emanuel Berg via Users list for the GNU Emacs text editor
2021-09-26  7:09   ` [External] : `max-specpdl-size' and `max-lisp-eval-depth' Hongyi Zhao

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fstpt04p.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=help-gnu-emacs@gnu.org \
    --cc=hongyi.zhao@gmail.com \
    --cc=larsi@gnus.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.