From: tb@becket.net (Thomas Bushnell, BSG)
Subject: module trickery
Date: 28 Aug 2002 16:28:14 -0700 [thread overview]
Message-ID: <87elcibm29.fsf@becket.becket.net> (raw)
I need to evaluate expressions in a defined module. I do this with:
(eval-in-module EXPR special-module)
special-module is very carefully constructed. It gets variable
definitions from certain other places, all of which work just fine. I
also need it to inherit syntax definitions from a specified module. I
use the following to grab the relevant syntax:
(module-use! special-module (resolve-module '(python syntax)))
The (python syntax) module creates syntax with define-syntax, and does
nothing out of the ordinary.
When I evaluate expressions in special-module which use the syntax
defined in (python syntax), things go into an infinite loop. The
macro I'm testing is blindingly simple and works fine in a normal
environment.
I am not wedded to this particular arrangement: anything that imports
the macros from one module to another works, provided I get to use
define-syntax.
What might I be doing wrong?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-08-28 23:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 23:28 Thomas Bushnell, BSG [this message]
2002-08-29 20:40 ` module trickery Marius Vollmer
2002-08-30 23:02 ` Thomas Bushnell, BSG
2002-08-31 2:58 ` Rob Browning
2002-08-31 15:01 ` Marius Vollmer
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=87elcibm29.fsf@becket.becket.net \
--to=tb@becket.net \
/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).