From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: Emacs variables (was: Bug in eval-string?)
Date: 31 Aug 2002 15:51:34 +0200 [thread overview]
Message-ID: <871y8fm909.fsf@zagadka.ping.de> (raw)
In-Reply-To: <uw51y8kjsgr.fsf_-_@saturn.math.uni-magdeburg.de>
Matthias Koeppe <mkoeppe@mail.Math.Uni-Magdeburg.De> writes:
> The point is that Emacs Lisp's dynamically-binding LET binds a
> _symbol_ to a fresh _location_ in its dynamic environment. This is
> semantically very different from a value-swapping FLUID-LET (in a
> multithreaded environment), no matter to which generalized location
> FLUID-LET is applied. This is not simply about the "exposition of
> Emacs variables to Scheme". It's about the implementation of dynamic
> scoping in a multithreaded environment.
I see now, thanks. I will have to think about this some more...
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-31 13:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 12:56 Bug in eval-string? rm
2002-08-08 21:03 ` Marius Vollmer
2002-08-09 9:06 ` Matthias Koeppe
2002-08-09 9:19 ` Marius Vollmer
2002-08-09 10:24 ` Matthias Koeppe
2002-08-10 14:18 ` Marius Vollmer
2002-08-12 18:20 ` Matthias Koeppe
2002-08-13 0:39 ` Marius Vollmer
2002-08-14 19:07 ` Marius Vollmer
2002-08-17 11:09 ` Neil Jerram
2002-08-20 11:39 ` Matthias Koeppe
2002-08-21 19:26 ` Marius Vollmer
2002-08-27 14:18 ` Emacs variables (was: Bug in eval-string?) Matthias Koeppe
2002-08-31 13:51 ` Marius Vollmer [this message]
2002-08-08 21:27 ` Bug in eval-string? Neil Jerram
2002-08-09 9:35 ` rm
2002-08-10 14:43 ` Marius Vollmer
2002-08-12 10:49 ` rm
2002-08-13 20:55 ` Marius Vollmer
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871y8fm909.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@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).