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: Mon, 8 Feb 2010 11:02:01 -0500 [thread overview]
Message-ID: <2bc5f8211002080802s186a1da1h1bce05ce5f32a8e2@mail.gmail.com> (raw)
In-Reply-To: <m3tyttbang.fsf@pobox.com>
Hi Andy,
> Will do, and thanks!!
No problem!
I'm running into some trouble, though, and I could use your (or
somebody's) help. I'm a little shaky on the details with regard to
the syntax-case expansion process, but I think the issue is that
during the expansion of a single top-level expression, the expansion
environment is constant. So the following (which is approximately
what "native" Guile modules do):
(define-module (my-module))
(use-modules ((my-syntax-transformer)))
[transformable-syntax]
...will properly expand and compile, since the expansion environment
for [transformable-syntax] reflects the updates to the module-uses
list made by `use-modules', whereas the following (which is
approximately what our R6RS library transformer produces):
(begin
(define-module (my-module))
(use-modules ((my-syntax-transformer)))
[transformable-syntax])
...won't properly expand macros whose transformers are defined in the
`(my-syntax-transformer)' module.
Does this sound plausible? I spent most of this past weekend trying
to grok this and work around it (via various `eval'-based
incantations) without much luck. (The weird part is, I don't recall
this happening with my old `(ice-9 r6rs-libraries)' module
implementation, but I could be wrong.)
Regards,
Julian
next prev parent reply other threads:[~2010-02-08 16:02 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
2010-02-06 17:50 ` Julian Graham
2010-02-07 10:30 ` Andy Wingo
2010-02-08 16:02 ` Julian Graham [this message]
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=2bc5f8211002080802s186a1da1h1bce05ce5f32a8e2@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).