From: Julian Graham <joolean@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: r6rs standard libraries
Date: Thu, 28 Jan 2010 22:52:57 -0500 [thread overview]
Message-ID: <2bc5f8211001281952v6d6d2e86g28b888f441547d72@mail.gmail.com> (raw)
In-Reply-To: <m3ocki1bn9.fsf@pobox.com>
Hi Andy,
> I also think we should have `library' and `import' in the basic
> environment. In order to do this I would like for them in boot-9.scm,
> not in a separate module, and implemented in terms of syntax-case.
>
> Implementing `library' in terms of syntax-case will allow `library' to
> expand out to (begin (define-module (foo) #:pure) (import a ...) ...),
> which allows imports to be processed only in the `import' macro. The
> `import' macro will be resolved in `(guile)' even though the module is
> pure, due to hygiene. No toplevel-defined helper functions will be
> necessary.
>
> Does this sound sensible to you?
It sure does. (Sorry about the delay in replying -- I haven't had a
lot of time for Guile this week, plus I wanted to let everyone resolve
their thinking about boot-9.) Just a warning, though: I may need some
syntax-case hand-holding.
> If so, can you make a git branch that (1) adds `library' and `import' to
> boot-9, then adds the other modules, one-by-one with tests? I've got my
> finger on the merge trigger :)
Will do.
Regards,
Julian
next prev parent reply other threads:[~2010-01-29 3:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 17:53 r6rs standard libraries Julian Graham
2010-01-25 14:50 ` Andy Wingo
2010-01-25 17:37 ` Ludovic Courtès
2010-01-25 21:41 ` Andy Wingo
2010-01-26 14:35 ` Ludovic Courtès
2010-01-26 19:35 ` Andy Wingo
2010-01-28 21:54 ` Neil Jerram
2010-01-29 3:04 ` Grant Rettke
2010-01-29 3:52 ` Julian Graham [this message]
2010-02-06 17:50 ` Julian Graham
2010-02-07 10:30 ` Andy Wingo
2010-02-08 16:02 ` Julian Graham
2010-02-15 20:33 ` Julian Graham
2010-02-24 5:47 ` Julian Graham
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=2bc5f8211001281952v6d6d2e86g28b888f441547d72@mail.gmail.com \
--to=joolean@gmail.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).