Re: loading a module via an absolute path

[Marius Vollmer]

address@hidden (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