From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: r6rs libraries
Date: Tue, 06 Jan 2009 00:40:49 +0100 [thread overview]
Message-ID: <8763kt48zi.fsf@gnu.org> (raw)
In-Reply-To: 2bc5f8210901012010g2ebb6effx5c966d0e26fe382b@mail.gmail.com
Hello and happy new year! :-)
"Julian Graham" <joolean@gmail.com> writes:
> * I think it'd be possible to implement R6RS "import levels" using
> Guile's existing #:export, #:export-syntax, #:reexpport, and
> #:reexport-syntax keywords -- if it weren't for the `(meta <level>)'
> option for import specifiers. It might still be possible, given the
> allowances of section 7.2. I don't know, I'm still trying to figure
> that out.
The problem is that Guile has *no* phase separation whatsoever: macros
are evaluated at run-time, in the same environment as actual code that's
executed.
This is different in the `vm' branch where, of course, macros are
expanded at compile-time in a compile-time environment. However, I
don't think the compiler supports phase specifiers in `define-module'
(e.g., `#:export-syntax' and `#:use-syntax' to export/import for
compile-time, etc.). Andy?
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-01-05 23:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 1:05 r6rs libraries (was Re: role of guile-lib) Julian Graham
2008-12-28 11:09 ` r6rs libraries Andy Wingo
2008-12-29 6:38 ` Julian Graham
2009-01-02 4:10 ` Julian Graham
2009-01-05 23:40 ` Ludovic Courtès [this message]
2009-01-06 9:45 ` Andy Wingo
2009-01-11 23:21 ` Julian Graham
2009-01-13 16:17 ` Ludovic Courtès
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=8763kt48zi.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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).