From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: module trickery
Date: 31 Aug 2002 17:01:30 +0200 [thread overview]
Message-ID: <87wuq7kr79.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87ptw0ymph.fsf@becket.becket.net>
tb@becket.net (Thomas Bushnell, BSG) writes:
> I'm quite flexible here... anything that lets me set up the relevant
> module and do eval-in-module will be fine by me. Switching from
> Guile 1.4 to the latest 1.5 test release is not unacceptible, if it
> will really work.
Here is something that works with 1.5.8 and CVS HEAD. I don't know
whether it works with the 1.4 series, tho. Is it similar enough to
what you are doing?
(define-module (python syntax)
:use-syntax (ice-9 syncase))
(define-syntax foo
(syntax-rules ()
((_ a)
(display a))))
(define-module (test))
(define python-toplevel (make-module))
(beautify-user-module! python-toplevel)
(module-use! python-toplevel (resolve-module '(python syntax)))
(eval '(foo "hi\n") python-toplevel)
Running it produces:
$ guile -s x.scm
hi
Thus, it seems that no additional tricks are needed, which is a good
thing.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-08-31 15:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 23:28 module trickery Thomas Bushnell, BSG
2002-08-29 20:40 ` Marius Vollmer
2002-08-30 23:02 ` Thomas Bushnell, BSG
2002-08-31 2:58 ` Rob Browning
2002-08-31 15:01 ` Marius Vollmer [this message]
2002-09-03 21:52 ` Thomas Bushnell, BSG
2002-09-03 22:11 ` Thomas Bushnell, BSG
2002-09-04 19:35 ` Marius Vollmer
2002-09-04 20:12 ` Tom Lord
2002-09-05 16:52 ` Marius Vollmer
2002-09-04 20:14 ` Marius Vollmer
2002-09-04 22:21 ` Thomas Bushnell, BSG
2002-09-04 22:40 ` Marius Vollmer
2002-09-04 23:33 ` Thomas Bushnell, BSG
[not found] ` <87r8g9uy8d.fsf@becket.becket.net>
2002-09-05 19:37 ` 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=87wuq7kr79.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--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).