Modularity in a cap-secure way

I've gained some good insights regarding modularity and
metaprogramming from these Newspeak papers:
 "Objects as Modules in Newspeak" http://bracha.org/newspeak-modules.pdf
 "Mirrors: design principles for meta-level facilities of
object-oriented programming languages" http://bracha.org/mirrors.pdf

The Objects as Modules paper in particular makes it clear to me how to
implement modules without a global namespace in the visual programming
language I'm working on.  Well, at the top level there is of course a
global namespace, but instead of an import statement that looks up the
appropriate module, you pass in the module to be bound to that named
interface.  Seems like the basic capability principle of passing in
the resources needed instead of looking them up.

Found via:
http://wadler.blogspot.com/2009/07/mirrors-design-principles-for-meta.html
http://wadler.blogspot.com/2009/08/objects-as-modules-in-newspeak.html

Enjoy,

Monty

(Note, I tried posting this to cap-talk last month but it's in limbo,
and also it seems to fit under the "other capability languages" part
of this list's description.)