From: Lynn Winebarger <owinebar@free-expression.org>
Cc: guile-devel@gnu.org
Subject: Re: comments on new-model.txt
Date: Sun, 8 Sep 2002 18:47:34 -0500 [thread overview]
Message-ID: <0209081847342E.19624@locke.free-expression.org> (raw)
In-Reply-To: <87n0qw45p4.fsf@zagadka.ping.de>
On Thursday 05 September 2002 14:06, Marius Vollmer wrote:
> Lynn Winebarger <owinebar@free-expression.org> writes:
> Ick, it's in CVS (workbook/compilation/), but I'm not yet really
> prepared to defend it! ;)
Well, when I saw it appear on guile-cvs, I had to check it out.
I'm surprised there haven't been other responses, but maybe
the beginning of the academic year affects a lot of people here.
I'm not ready to respond completely, but I can clarify something.
> > Rather than tying imported variables to solely to modules, I
> > believe GUILE should adopt 2 new types of variables, extloc and
> > extvar (or whatever) corresponding to ilocs and variables, but
> > carrying a reference to their environment with them. Space might be
> > conserved by pointing into a table of environments rather than using
> > a whole pointer. In this way we can untie option 2 from options 1
> > and 3.
>
So, we have two SCM types, ilocs and variables (actually variable bindings,
but we can leave that for later). ilocs always look up their values in the
data environment of their closure, and variables are just pointers to a
storage location. An extloc would be like an iloc (that is, a frame offset
and distance in a frame), but would be stored in a cell where the second
word pointed to the data environment to look it up in (the first word would
contain the frame offset and distance). Likewise an extvarref would
contain both the pointer to the binding and some way of identifying
what top-level environment it's from.
This would be a convenient way to represent imported variables.
The only concrete reason I can offer for including a pointer (of some
form) to the top level environment of an external variable (actually
any top-level variable) is for ones that aren't bound at the time
of parsing (recalling that correct macro expansion can't be lazy in
the presence of side-effects, as some of the syntax-case examples
I've been posting should demonstrate). I have a feeling that the pointer
to the top-level environment might turn out to be useful in some other
way, but I couldn't say what that would be.
Lynn
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-09-08 23:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 1:22 comments on new-model.txt Lynn Winebarger
2002-09-05 19:06 ` Marius Vollmer
2002-09-08 23:47 ` Lynn Winebarger [this message]
2002-09-09 22:55 ` Marius Vollmer
2002-09-10 0:30 ` Lynn Winebarger
2002-09-10 0:32 ` Lynn Winebarger
2002-09-10 19:56 ` Marius Vollmer
2002-09-10 23:15 ` Tom Lord
2002-09-11 17:38 ` Marius Vollmer
2002-09-11 7:28 ` Lynn Winebarger
2002-09-11 18:11 ` Marius Vollmer
2002-09-14 3:18 ` comments on new-model.txt [long] Lynn Winebarger
2002-09-22 22:13 ` Marius Vollmer
2002-09-24 20:03 ` Marius Vollmer
2002-09-28 23:01 ` Lynn Winebarger
2002-10-12 13:35 ` 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=0209081847342E.19624@locke.free-expression.org \
--to=owinebar@free-expression.org \
--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).