From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: New syntax: (: MODULE-NAME VARIABLE-NAME)
Date: Thu, 13 Nov 2003 21:58:56 +0100 [thread overview]
Message-ID: <873ccsugrz.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m33ccs126j.fsf@laruns.ossau.uklinux.net> (Neil Jerram's message of "13 Nov 2003 19:47:00 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
> Marius> You don't need to 'use' that module first.
>
> But a use of `:' on a module that hasn't been loaded yet will cause an
> implicit `(use-modules ...)', won't it, which could in turn do
> arbitrary evaluation? Is so, is this OK?
Good point. Hmm. We already have this kind of behavior with the
:autoload option. In any case, I think we can allow this. I'd say it
is somewhat like macros, you don't know when they are expanded
exactly, and you have to account for this. Likewise, you can't know
when a module is loaded, so you need to account for that, too.
--
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:[~2003-11-13 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 18:12 New syntax: (: MODULE-NAME VARIABLE-NAME) Marius Vollmer
2003-11-13 19:47 ` Neil Jerram
2003-11-13 20:58 ` Marius Vollmer [this message]
2003-11-14 21:04 ` Neil Jerram
2003-11-15 15:19 ` Marius Vollmer
2003-11-15 19:22 ` Neil Jerram
2003-11-16 17:31 ` Marius Vollmer
2003-11-16 18:20 ` Neil Jerram
2003-11-16 18:38 ` Neil Jerram
2003-11-16 20:36 ` Marius Vollmer
2003-11-17 20:18 ` Neil Jerram
2003-11-17 21:34 ` Marius Vollmer
2003-11-16 20:28 ` Marius Vollmer
2003-11-14 22:09 ` Mikael Djurfeldt
2003-11-15 15:10 ` Marius Vollmer
2003-11-17 2:00 ` Mikael Djurfeldt
2003-11-17 14:41 ` Marius Vollmer
2003-11-16 8:02 ` Dirk Herrmann
2003-11-17 14:44 ` New syntax (@ MODULE-NAME VARIABLE-NAME) committed 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=873ccsugrz.fsf@zagadka.ping.de \
--to=mvo@zagadka.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).