unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: loading a module via an absolute path
Date: Fri, 18 Oct 2002 14:21:35 -0400	[thread overview]
Message-ID: <m3bs5robei.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87vg4gl4g3.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Sat, 05 Oct 2002 20:51:56 -0500")

Ok, I got my modules-with-absolute-paths working, but there is
noticeable friction between it and use-modules.  Is there any chance
of extending use-modules (or providing a cooperating procedure) to
allow things like:
(use-modules ("/path/to/foo.scm" :select ...))
?

Rob Browning <rlb@defaultvalue.org> wrote:
>   guile> (use-modules (ice-9 safe))
>   guile> (define msm (make-safe-module))

The main problem I've had with this is that it's too safe.  How do I
create a module with the same bindings as the original "root" module,
after boot-9, etc., was loaded in it?  I.e., the kind use-modules
creates for the libraries it loads?  If there's a way to iterate over
the bindings in a module, I guess I could add them one by one with
module-define!.

>   guile> (module-use! (current-module) msm)
>   #f

Ah - would (module-use! msm (current-module)) do what I want?  Or
would that risk creating a harmful loop if I also import bindings the
other way?


paul


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


  parent reply	other threads:[~2002-10-18 18:21 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 [this message]
2002-10-18 22:26     ` Marius Vollmer
2002-10-18 23:26       ` Paul Jarc
2002-10-19 10:44         ` Marius Vollmer
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=m3bs5robei.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).