On Sun, Jun 29, 2008 at 5:58 AM, Ken G. Brown <kbrown at mac.com> wrote:

>
> I'm thinking a significant part of the problem of namespaces, version
> control, package loading and image release compatibility is that many
> versions of methods and classes can exist in the wild but the names do not
> include any information about their uniqueness. So when you load something
> it may stomp on methods that are still required in their previous
> incarnation for something else to work.
>


My Package/Namespaces architecture was designed to solve the problems of
namespaces, version control, atomic package loading, and package
interdependence. In theory at least, a loaded package will run in exactly
the same environment it was written and tested in, even to the extent of
automatically loading that environment into the image if need be.

These are unstructured braindumps of what I've been working on:
http://gulik.pbwiki.com/Namespaces
http://gulik.pbwiki.com/Packages

I'm now writing tests and fixing up bugs in the core code. An alpha release
will be made "soon".

I'm designing these Namespaces for a fork of Squeak called SecureSqueak
which is designed to run untrusted code in a secure sandbox. It is not
intended for general use in Squeak.

Gulik.


-- 
http://people.squeakfoundation.org/person/mikevdg
http://gulik.pbwiki.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20080630/e0781de3/attachment.htm