Re: ideal way to load modules / set up evaluation environments at runtime.

Roderic Morris <[email protected]> writes:

> Ah, cool! Thanks for the ref. Unfortunately, it seems that library
> doesn't work for the same reason the code I have no doesn't: the
> config-package function from the package-commands-internal-interface
> module is a "user-context-accessor", and it seems user-context doesn't
> exist outside of the command processor. Calling load-config-file from
> that library gives the following error:
>
> error: unhandled upcall [propogate-upcall]
>        #{upcall-token user-session}
>
>
> I'm not sure what the right way to deal with this is. Is there a
> canonical config-package outside of the command processor?

I'm a bit confused: The "default" config package is indeed something
associated with the user session: There's no concept of "canonical
config package" outside of that.  What you can always do is construct or
pass around a config package explicitly.  Could you elaborate on what
you're trying to do?

-- 
Regards,
Mike