Re: Refactoring dynamic roots

[Marius Vollmer <marius.vollmer@uni-dortmund.de>]

Kevin Ryde <user42@zip.com.au> writes:

> Marius Vollmer <mvo@zagadka.de> writes:
>>
>> you want to give it its own dynamic state because that is very
>> useful.
>
> Do you have an example in mind?

Hmm, maybe running a repl: the code managing the repl and the cde that
is actually evaluated in it might each want to have their own dynamic
state.  For example, the current module of the evaluated code will
likely be different from the current module of the code that manages
the repl.

The behavior of eval would become more clean, in general.  For
example

  (eval '(define-module (foo)) (current-module))

will temporarily set the current module to (foo) as a side effect of
define-module, but eval will revert it to the module that was current
when eval was called.  If you want the current module change to stick,
you would have to use primitive-eval.

In contrast, you could use a dynamic state to carry 'dynamic state
information' from one call to eval to the next but while still being
isolated from changes to this state.


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