From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: macros, procedure->macro
Date: 13 Jul 2002 20:38:44 +0200 [thread overview]
Message-ID: <87d6tro4ln.fsf@zagadka.ping.de> (raw)
In-Reply-To: Pine.GSO.4.05.10207131148030.21457-100000@sallust.ida.ing.tu-bs.de
Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de> writes:
> I have decided for the solution above to avoid having to export an
> additional binding.
I hope that we can avoid exporting bindings that are only used in
macro expansions. I don't know exactly how (ice-9 syncase) deals with
this right now, but I'd say it is supposed to make the following work:
(define-module (t1)
:use-syntax (ice-9 syncase)
:export-syntax foo)
(define (bar) #t)
(define-syntax foo
(syntax-rules ()
((foo)
(bar))))
(define-module (t2)
:use-syntax (ice-9 syncase)
:use-module (t1))
(foo)
Note that (t1) doesn't export bar, but the expansion of (foo) uses it.
I have some vague ideas of how to implement this... the basic one is
to add new syntax that allows one to refer to specific bindings from
specific modules, on a very low level. For example, we could use
(#:module-ref (t1) bar)
to get at the bar binding of the (t1) module, from anywhere. Note
that we use a keyword in the operator position.
(ice-9 syncase) could then rewrite references to global variables to
use this form.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-13 18:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87n0t376c9.fsf@zagadka.ping.de>
2002-07-08 20:23 ` macros, procedure->macro Dirk Herrmann
2002-07-09 18:13 ` Marius Vollmer
2002-07-10 21:54 ` Dirk Herrmann
2002-07-13 9:53 ` Dirk Herrmann
2002-07-13 18:38 ` Marius Vollmer [this message]
[not found] <m3lm8e5o69.fsf@laruns.ossau.uklinux.net>
2002-07-14 21:35 ` Dirk Herrmann
2002-07-15 20:48 ` Marius Vollmer
2002-07-15 22:42 ` Neil Jerram
2002-07-16 22:00 ` Dirk Herrmann
[not found] <200207012220.PAA08054@onyx.he.net>
2002-07-03 20:08 ` Dirk Herrmann
2002-07-04 20:16 ` Dirk Herrmann
2002-07-07 18:15 ` Marius Vollmer
2002-07-01 19:56 Dirk Herrmann
2002-07-01 21:30 ` Rob Browning
2002-07-03 20:24 ` Dirk Herrmann
2002-07-01 22:14 ` Marius Vollmer
2002-07-03 20:11 ` Dirk Herrmann
2002-07-07 17:54 ` Marius Vollmer
2002-07-08 20:31 ` Dirk Herrmann
2002-07-09 18:22 ` Marius Vollmer
2002-07-10 5:21 ` Dirk Herrmann
2002-07-10 19:31 ` Marius Vollmer
2002-07-10 19:57 ` Dirk Herrmann
2002-07-10 20:08 ` Marius Vollmer
2002-07-01 22:17 ` Gary Houston
2002-07-09 21:16 ` Neil Jerram
2002-07-10 5:46 ` Dirk Herrmann
2002-07-10 10:15 ` Neil Jerram
2002-07-10 20:03 ` Dirk Herrmann
2002-07-13 0:09 ` Neil Jerram
2002-07-13 2:36 ` Clinton Ebadi
2002-07-14 15:23 ` Neil Jerram
2002-07-14 16:26 ` Marius Vollmer
2002-07-15 6:03 ` Rob Browning
2002-07-13 6:53 ` Dirk Herrmann
2002-07-14 15:23 ` Neil Jerram
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=87d6tro4ln.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@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).