Do we already have docs about modules, loading (non-toplevel), etc.

[Rob Browning]

Do we have any docs (or is anyone already planning to write docs)
about the interactions between load, eval, define-module, use-modules,
gh_eval_str, gh_lookup, (define foo (lambda ...)) and the current
module[1]?

i.e. I'm thinking of discussions of things like this:

  (define-module (some-module))
  (export foo)
  (define (foo)
    (load some-file))

  (define-module (some-other-module))
  (use-modules (some-module))
  (foo)

What's the current module when some-file is loaded?  Where do any
exports in there go? etc.  How do published C functions fit into the
picture?  In particular what's the defined behavior of
gh_eval_str/gh_lookup wrt the module system, etc.

If we don't already have such docs, I'm thinking of writing them.  If
we want guile to be an extension language I think we may need clearer
guidance on these issues.  IMO they can be somewhat confusing.

[1] where I presume we need to talk about the difference between the
current-module at run-time and the current module at the time a
closure is captured.  What exactly are the rules?

-- 
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