Hi,
Andy Wingo wi...@pobox.com writes:
Hi,
On Thu 08 Apr 2010 01:01, l...@gnu.org (Ludovic Courtès) writes:
Julian Graham jool...@gmail.com writes:
I'm still inclined to think that the module namespace hierarchy (and it
is a hierarchy) should not impinge on the environment of an
Hi Andy and Ludo,
I'm still inclined to think that the module namespace hierarchy (and it
is a hierarchy) should not impinge on the environment of an evaluation.
But, not something we can change right now.
This is actually causing me some difficulty -- I'm implementing the
R6RS composite
Hi,
Julian Graham jool...@gmail.com writes:
I'm still inclined to think that the module namespace hierarchy (and it
is a hierarchy) should not impinge on the environment of an evaluation.
But, not something we can change right now.
This is actually causing me some difficulty -- I'm
for the hierarchical name space. :-)
Suppose we want something like PLaneT or Eggs, let’s call it GUMM
(Guile’s Unified Module Machinery). Ideally, we’d want to be able to
write this:
(use-modules (gumm foo bar))
Such that:
- If a (foo bar) module exists locally, it is used
- else