unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Chris Vine <chris@cvine.freeserve.co.uk>
To: guile-user@gnu.org
Subject: Re: Transient environment with standard functions
Date: Fri, 10 Jun 2016 23:35:28 +0100	[thread overview]
Message-ID: <20160610233528.0f568f8d@laptop.homenet> (raw)
In-Reply-To: <7B7BC3F7-A25D-427D-8E21-D3583C3C7DEA@gmail.com>

On Fri, 10 Jun 2016 14:44:43 -0400
Matthew Keeter <matt.j.keeter@gmail.com> wrote:
> Thanks for the reply!
> 
> You’ll be sad to hear that I’ve solved the problem by switching to
> Racket – (make-base-namespace) creates the kind of temporary
> environment I needed, and multiple calls produce multiple independent
> namespaces.

With guile, the undocumented 'make-fresh-user-module' procedure probably
does what you want.  It constructs a new top level for the thread of
execution which calls it, which is unique as against any other top
level. Whether it is what you want depends on what you mean by an
"environment", which is not necessarily the same as a "namespace".  If
you are after a new namespace, make-fresh-user-module should do it.



  parent reply	other threads:[~2016-06-10 22:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-28 20:16 Transient environment with standard functions Matthew Keeter
2016-06-10 18:18 ` Basa Centro
2016-06-10 18:44   ` Matthew Keeter
2016-06-10 20:39     ` Basa Centro
2016-06-10 21:11       ` Taylan Ulrich Bayırlı/Kammer
2016-06-10 22:11         ` Basa Centro
2016-06-10 22:31           ` Matthew Keeter
2016-06-10 22:49             ` Mike Gran
2016-06-10 23:08             ` Taylan Ulrich Bayırlı/Kammer
2016-06-11 15:15             ` Basa Centro
2016-06-11 19:44               ` Matthew Keeter
2016-06-10 22:35     ` Chris Vine [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-11 23:07 Basa Centro
2016-06-12  0:51 Basa Centro
2016-06-26 21:29 ` Amirouche Boubekki
2016-07-03 21:20 Blanka Herono

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=20160610233528.0f568f8d@laptop.homenet \
    --to=chris@cvine.freeserve.co.uk \
    --cc=guile-user@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).