unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
Subject: Re: loading a module via an absolute path
Date: 19 Oct 2002 12:44:22 +0200	[thread overview]
Message-ID: <87iszyzp15.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m365vzmiqn.fsf@multivac.cwru.edu>

prj@po.cwru.edu (Paul Jarc) writes:

> That's not quite what I'm looking for.  The way I did it, I don't use
> define-module at all; the imported code doesn't know or care what name
> the importing code uses to refer to it.  The loader procedure takes
> care of creating a new (anonymous) module, and loads the code into it.

I see.  You shouldn't use 'use-modules' for it, then.  It is better to
give this new concept a new set of functions to work with it.

> I'd be happy to keep using my loader, except that the modules it
> creates (with make-safe-module) are too sparse - lacking useful
> things like, say, defined?.  OTOH, a library loaded by use-modules
> has all the normal bindings at its disposal.  How can I create a
> module like that?

You can use

  (make-module 1021 (list (resolve-interface '(guile))))

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2002-10-19 10:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04 22:41 loading a module via an absolute path Paul Jarc
2002-10-06  1:51 ` Rob Browning
2002-10-07 17:09   ` Paul Jarc
2002-10-07 20:05   ` Paul Jarc
2002-10-18 18:21   ` Paul Jarc
2002-10-18 22:26     ` Marius Vollmer
2002-10-18 23:26       ` Paul Jarc
2002-10-19 10:44         ` Marius Vollmer [this message]
2002-10-19 20:42           ` Paul Jarc
2002-10-20 16:19             ` 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=87iszyzp15.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.de \
    /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).