Re: subverting use-modules restriction + module system RFD

[Rob Browning]

Marius Vollmer <address@hidden> writes:

> I prefer a more explicit style that doesn't rely on the `current
> module'.  The current module concept is mainly useful while loading
> and executing top-level forms, but it is not really meaningful for
> code that is executed not a top-level (i.e. closures).
>
>     (define (runtime-use-module module name)
>       (module-use! module (resolve-interface name)))

I prefer this too.

> This is probably only an implementation artifact however, and might
> vanish.  That is, `begin' subforms will always be on top-level when
> the begin is, but for the rest I'm not sure.

Right, and in particular, as we start to consider compilation, we'll
need some explicit "rules" about these kinds of expectations (if there
are any) so that we can make sure we know which behaviors we want/need
to preserve.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD