From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: David Kastrup <dak@gnu.org>
Cc: handa@ni.aist.go.jp, emacs-devel@gnu.org, rms@gnu.org,
Stefan Monnier <monnier@iro.umontreal.ca>,
miles@gnu.org
Subject: Re: (aset UNIBYTE-STRING MULTIBYTE-CHAR)
Date: Fri, 15 Feb 2008 10:08:40 +0900 [thread overview]
Message-ID: <878x1n6n6v.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <85ejbfyxfh.fsf@lola.goethe.zz>
David Kastrup writes:
> Richard Stallman <rms@gnu.org> writes:
>
> > While I don't consider Python as the best design by far (the lack
> > of type system rules it out right away), Elisp's dynamic scoping
> > mixed with buffer-local and frame-local and terminal-local
> > variables is pretty horrendous,
> >
> > I think it is elegant. Dynamic scoping is absolutely essential for an
> > Emacs-like editor, as explained in the Emacs paper from 1981.
>
> Shhhhh. Stefan is still in Cc, and he'll be sad to hear that his
> lexbind branch can't possibly exist.
No problema, amigos. From the cited paper (SIGOA 1981, 2:1-2):
It is not necessary for dynamic scope to be the *only* scope rule
available, just useful for it to be available.
(Isn't it Miles who is maintaining the lexbind branch? But he's
there, too. :-)
next prev parent reply other threads:[~2008-02-15 1:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 2:36 (aset UNIBYTE-STRING MULTIBYTE-CHAR) Kenichi Handa
2008-02-13 2:49 ` Stefan Monnier
2008-02-13 3:48 ` Kenichi Handa
2008-02-13 15:33 ` Stefan Monnier
2008-02-13 18:06 ` Stephen J. Turnbull
2008-02-13 19:33 ` Stefan Monnier
2008-02-13 22:49 ` Miles Bader
2008-02-14 1:11 ` Stephen J. Turnbull
2008-02-14 1:17 ` Miles Bader
2008-02-14 1:40 ` Stefan Monnier
2008-02-14 1:49 ` Miles Bader
2008-02-14 18:10 ` Richard Stallman
2008-02-14 22:40 ` David Kastrup
2008-02-15 1:08 ` Stephen J. Turnbull [this message]
2008-02-15 1:17 ` Miles Bader
2008-02-15 7:27 ` David Kastrup
2008-02-15 12:58 ` Richard Stallman
2008-02-14 23:37 ` Leo
2008-02-15 12:59 ` Richard Stallman
2008-02-14 4:20 ` Stephen J. Turnbull
2008-02-14 4:42 ` Richard Stallman
2008-02-15 1:39 ` Kenichi Handa
2008-02-15 4:27 ` Stefan Monnier
2008-02-15 8:42 ` Eli Zaretskii
2008-02-15 8:53 ` Miles Bader
2008-02-16 12:55 ` Eli Zaretskii
2008-02-16 5:53 ` Richard Stallman
2008-02-16 14:33 ` Stefan Monnier
2008-02-17 20:29 ` Richard Stallman
2008-02-18 1:15 ` Stefan Monnier
2008-02-18 4:00 ` Kenichi Handa
2008-02-18 17:31 ` Richard Stallman
2008-02-13 22:01 ` Richard Stallman
2008-02-13 23:13 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2008-04-15 7:11 Kenichi Handa
2008-04-15 15:52 ` Stefan Monnier
2008-04-17 1:13 ` Kenichi Handa
2008-05-07 19:31 Harald Hanche-Olsen
2008-05-14 6:54 ` Harald Hanche-Olsen
2008-05-14 12:22 ` Stefan Monnier
2008-05-14 12:50 ` Harald Hanche-Olsen
2008-05-15 1:18 ` Stefan Monnier
2008-05-15 6:11 ` Harald Hanche-Olsen
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=878x1n6n6v.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@ni.aist.go.jp \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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.
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).