> If things are loaded twice, that's definitely a bug.
Hard to tell. They are not autoloaded twice, but loading something
with `load' does not prevent the autoloader from loading it again.
> The rationale for ":use-module #/package/mod" loading both "package"
> and "package/mod" seems to be that, if you have a module with
> subdirectories, you can put definitions appropriate for all
> package/foo modules in package, and it'll automatically get loaded.
> However, I don't see that this is more useful than simply having
> package/mod do a :use-module on package; the latter seems clearer to
> me, anyway.
Yes, and in the case you dont want the directory module loaded, you
can't prevent it. The load-path can point anywhere and in my setup, I
have a subdirectory with name of my package that contains all Scheme
code and also a Scheme script in the current directory with the name
of the package that gets the whole thing going. When the package is
installed, this shouldn't be a problem, because the script wouldn't
probably be in the load-path, but who knows.
> If Tom Lord is on this list anymore, maybe he could explain.
Right now, I am waiting for my changes to get comitted. Something is
hanging somewhere, maybe they get thru, maybe not. *sigh*