From: Mike Gran <spk121@yahoo.com>
To: Matthew Keeter <matt.j.keeter@gmail.com>,
Basa Centro <basa.centro@gmail.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Transient environment with standard functions
Date: Fri, 10 Jun 2016 22:49:18 +0000 (UTC) [thread overview]
Message-ID: <280098050.902062.1465598958969.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <DDAE98E3-EDB4-4C2E-8F1E-89C470505DBB@gmail.com>
> On Friday, June 10, 2016 3:31 PM, Matthew Keeter <matt.j.keeter@gmail.com> wrote:
> > The specific use case is for dataflow graphs, where you’re evaluating a bunch of
> small
> snippets of code that can refer to each other by name.
>
> I’d like to make an environment in which the variables in the same subgraph are
> exposed as no-argument thunks.
>
> For example, let’s say I have one subgraph that contains
> a = “12” => evaluates to 12
> b = “(+ 1 (a))” => evaluates to 13, since the (a) thunk evaluates to 12
>
> and another subgraph which contains
> x = “1” => evaluates to 1
> y = “(* (x) 2)” => evaluates to 2
>
> If I insert the thunks into (scheme-report-environment 5), they leak from one
> graph
> to another – and to be fair, the docs to say that assigning into this
> environment is
> undefined behavior.
>
> However, if I make an empty environment with (null-environment), it doesn’t have
> useful functions like + and *; looks like (make-module) has the same issue.
>
> I'm sure that this is possible in Guile, but I got tired of reading through
> the source
> files to hunt down undocumented function that do what I need [1].
>
> -Matt
>
> [1] Another recent incident: How do you programmatically list all of the
> variables in a module?
> You search the web, find http://www.draketo.de/proj/guile-basics/#sec-3-2, see a
> a reference to
> module-map, which doesn’t exist in the documentation, dig it up in the source to
> see its
> arguments, etc…
I used something like this, once.
(define (buffer-local-variables)
"Return a list of the buffer-local variables in the current buffer"
(hash-map->list cons (module-obarray (current-module))))
See it in context here.
https://github.com/spk121/zile/blob/guile/src/zile.scm
-Mike
next prev parent reply other threads:[~2016-06-10 22:49 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 [this message]
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
-- 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=280098050.902062.1465598958969.JavaMail.yahoo@mail.yahoo.com \
--to=spk121@yahoo.com \
--cc=basa.centro@gmail.com \
--cc=guile-user@gnu.org \
--cc=matt.j.keeter@gmail.com \
/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).