From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: new-model.text, please comment
Date: Thu, 12 Sep 2002 18:28:30 -0500 [thread overview]
Message-ID: <87elby23fl.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <871y80tn9r.fsf@zagadka.ping.de> (Marius Vollmer's message of "11 Sep 2002 20:05:36 +0200")
Marius Vollmer <mvo@zagadka.ping.de> writes:
> I have written down my thoughts about an evaluation model that allows
> an optimizing ahead-of-time compiler. It's in CVS:
>
> guile/workbook/compilation/new-model.text
>
> Please have a look and comment on it.
I've read it through once, though I need to do so again, before
commenting much, but one part wasn't completely clear to me:
> The compiler is free to reuse top-level frames for several top-level
> forms, even when executing a form will change the name/module mapping
> used in the next. You must explicitely tell the compiler that it must
> construct a new top-level frame. You can do this with the
>
> (:module-barrier) XXX - need better name
>
> compiler directive. The directive guarantees that code prior to it is
> fully executed before top-level frames for forms after it are
> constructed. The directive must be a top-level form.
Could you provide a bit of elaboration here. More specifically, what
does "fully executed" mean? (I tend to start thinking of
"define-macro" when I hear that, though I guess any top-level form,
macro or not could be relevant.) For example, does the above mean
that given the following code:
(foo ...)
(do-something-that-changes-the-current-module!)
(bar ...)
the results would be undefined because the compiler is within its
rights to presume that do-something *doesn't* change the current
module unless a without a :module-barrier call like so:
(foo ...)
(do-something-that-changes-the-current-module!)
(:module-barrier)
(bar ...)
This seems to be implied by the later examples of use-modules, etc.,
but I just wanted to make sure I understood what you were stating.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-09-12 23:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 18:05 new-model.text, please comment Marius Vollmer
2002-09-12 22:48 ` Tom Lord
2002-09-14 22:48 ` Marius Vollmer
2002-09-15 0:50 ` Tom Lord
2002-09-15 0:55 ` Tom Lord
2002-09-21 20:27 ` Marius Vollmer
2002-09-12 23:28 ` Rob Browning [this message]
2002-09-13 20:22 ` Marius Vollmer
2002-09-13 20:34 ` Rob Browning
2002-09-13 18:53 ` Neil Jerram
2002-09-13 22:06 ` Rob Browning
2002-09-14 1:15 ` Lynn Winebarger
2002-09-14 22:05 ` 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=87elby23fl.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).