unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: jyavner@member.fsf.org, emacs-devel@gnu.org
Subject: Re: "Misunderstanding of the lambda calculus"
Date: Wed, 01 Feb 2006 14:38:35 -0500	[thread overview]
Message-ID: <E1F4NoJ-0000Ah-DF@fencepost.gnu.org> (raw)
In-Reply-To: <87y80wkxbd.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 31 Jan 2006 15:09:08 -0500)

    It should probably say something like "older Lisps", since it is indeed
    a fact (AFAIK) that all Lisps defined "recently" (around the time or
    EuLisp, Common Lisp, Scheme, ...) use lexical scoping by default.

Emacs Lisp was defined in 1984, which makes it newer than Common Lisp
or Scheme.

    As for efficiency: except for naive interpreters, static scoping is
    generally more rather than less efficient.

I only know how to write a naive interpreter.  Anyway, having
implemented static scoping in an interpreter for Common Lisp, I wanted
nothing like that again!

  reply	other threads:[~2006-02-01 19:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1F3FdP-0002xe-OW@monty-python.gnu.org>
2006-01-29 17:51 ` "Misunderstanding of the lambda calculus" Jonathan Yavner
2006-01-29 18:32   ` David Kastrup
2006-01-30 18:46     ` Richard M. Stallman
2006-01-30 19:28       ` David Kastrup
2006-01-31 18:03         ` Richard M. Stallman
2006-01-31 19:47           ` Kevin Rodgers
2006-01-31 20:09           ` Stefan Monnier
2006-02-01 19:38             ` Richard M. Stallman [this message]
2006-01-31 21:57           ` David Kastrup
2006-02-01  8:12             ` Alan Mackenzie
2006-02-01  8:52               ` David Kastrup
2006-02-01 10:40                 ` Miles Bader
2006-02-01 15:01                   ` Jonathan Yavner
2006-02-01 19:39             ` Richard M. Stallman
2006-01-29  5:42 Chong Yidong

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=E1F4NoJ-0000Ah-DF@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jyavner@member.fsf.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).