Wow, interesting reading, thanks. So problem is not in getting into the
module, but instead in dynamic recompilation of dependencies inside that
module. Probably I should postpone my idea for future releases with that
issues resolved.
On Mon, Sep 8, 2014 at 1:23 AM, Isaiah Norton
Yes. The recommended work-around/workflow is to make changes within the
module declaration, and call `reload` to get those changes. It's a similar
issue to what is discussed here:
https://github.com/JuliaLang/julia/issues/265
(and could potentially be changed whenever that is resolved)
This might
I believe this is not currently exposed, although it may be worth pointing
out that any internal variable from an imported module is readable with
`MyModule.foo`. Julia modules are closed after declaration, although you
can sort of cheat by calling `MyModule.eval(::Expr) -- the downside being
In module.c in Julia sources I see jl_set_current_module() function. Is
it somehow exposed to Julia API?
To give you some context, in Common Lisp (as well as some other dialects)
there are 2 separate macros for dealing with packages (analogue of modules
in Julia):
defpackage - defines new
