From: Thien-Thi Nguyen <ttn@surf.glug.org>
Cc: guile-user@gnu.org
Subject: Re: modules
Date: Sun, 21 Mar 2004 22:29:39 +0100 [thread overview]
Message-ID: <E1B5AVn-0007XF-00@surf.glug.org> (raw)
In-Reply-To: <877jxeahbn.fsf@buug.org> (message from Ian Zimmerman on 20 Mar 2004 21:40:28 -0800)
From: Ian Zimmerman <itz@buug.org>
Date: 20 Mar 2004 21:40:28 -0800
How can I customize a module during loading?
for the present, you have to fake it w/ `load' and closures.
for the future, you can propose a design for a (sub-)clause for
`use-modules' or `define-module' that supports parameterized modules,
and then work w/ the module system that implements your design (after
some likely-to-be-lengthly period of debugging ;-).
how can I get an actual module object?
use `resolve-module'. for example:
(eval-in-module '(current-module) (resolve-module '(ice-9 rw)))
=> #<directory (ice-9 rw) 4024bd38>
i have discovered there are actually three kinds of "actual module
object" in the context of guile -- one kind you can see in the above
example (the "directory"), the other two normally more transient but
nonetheless exposed/exposable. the word "module" is the chicken of
programming terms -- everything tastes like it...
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-03-21 21:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 5:40 modules Ian Zimmerman
2004-03-21 14:47 ` modules Andreas Rottmann
2004-03-22 18:05 ` modules Ian Zimmerman
2004-03-23 16:05 ` modules Robert Uhl
2004-03-21 21:29 ` Thien-Thi Nguyen [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-08 11:45 Modules Marek Kubica
2010-12-08 18:11 ` Modules Andreas Rottmann
2010-12-09 1:19 ` Modules Nala Ginrut
2011-01-28 16:26 ` Modules Andy Wingo
2011-01-29 12:13 ` Modules Marek Kubica
2011-01-29 13:08 ` Modules Neil Jerram
2011-01-29 13:18 ` Modules Neil Jerram
2011-01-29 17:04 ` Modules Andy Wingo
2011-01-29 18:37 ` Modules Marek Kubica
2011-01-29 23:17 ` Modules Neil Jerram
2011-01-30 10:13 ` Modules Thien-Thi Nguyen
2011-01-30 11:42 ` Modules Andy Wingo
2011-02-13 19:05 ` Modules Andy Wingo
2011-01-29 17:07 ` Modules Andy Wingo
2011-01-29 18:40 ` Modules Marek Kubica
2011-01-29 23:35 ` Modules Neil Jerram
2011-02-01 21:43 ` Modules Andy Wingo
2011-02-02 14:43 ` Modules Jon Wilson
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=E1B5AVn-0007XF-00@surf.glug.org \
--to=ttn@surf.glug.org \
--cc=guile-user@gnu.org \
--cc=ttn@glug.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).