Hey Rob,

On Wed, 2004-06-30 at 17:20 -0500, Rob Browning wrote:
> For what it's worth, one part that I snipped from my earlier message
> (just to make it more concise) basically agress with you here.

That's cool. It's good to see we have a consensus about something :-)

> more concretely, say (slib format), (slib uri), and (slib posix-time),
>  if slib were represented directly as guile modules.

This is interesting! I think I know how it could be done, too. Set a
custom module binder proc to (slib). Since submodules are (stupidly!)
bound to symbols within the parent module, we could catch undefined
symbols, and then require the lib. Bling. The tricky thing would be to
make sure that the interface of the modules doesn't also exhibit this
behavior.

Oh this is interesting indeed. I hacked up a prototype, and attached it.
First you have to use (slib), which sets up the lazy binder. Then when
you use (slib foo), it tries to require the foo. It's very much tied to
guile's module implementation, which is pretty evil, but it does work:

(use-modules ((slib) (slib stdio)))
(printf "%s" "Hello world!")
=| Hello world!

-- 
Andy Wingo <wingo@pobox.com>
http://ambient.2y.net/wingo/