From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Static Scoping versus Dynamic Scoping
Date: Sat, 09 Jun 2007 17:58:04 -0400 [thread overview]
Message-ID: <jwvabv8bxne.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 1179043947.214708.291260@e51g2000hsg.googlegroups.com
> I read somewhere that in the future dynamic scoping of variables in Emacs
> Lisp will be replaced with static scoping.
You're confused. There is some work going on which attempts to *add*
static scoping (more seriously than provided by CL's lexical-let macro).
But there's no intention to drop dynamic scoping: it would break about 99%
of existing Lisp code.
Stefan
next prev parent reply other threads:[~2007-06-09 21:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 8:12 Static Scoping versus Dynamic Scoping Davin Pearson
2007-05-13 8:31 ` David Kastrup
2007-06-09 21:58 ` Stefan Monnier [this message]
2007-06-10 4:44 ` Tom Tromey
[not found] ` <mailman.1845.1181451756.32220.help-gnu-emacs@gnu.org>
2007-06-12 14:19 ` 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=jwvabv8bxne.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@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.
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).