<br><br><div class="gmail_quote">On Sun, Jun 29, 2008 at 5:58 AM, Ken G. Brown <<a href="mailto:kbrown@mac.com">kbrown@mac.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
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.<br>
</blockquote></div><br><br>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. <br>
<br>These are unstructured braindumps of what I've been working on:<br><a href="http://gulik.pbwiki.com/Namespaces">http://gulik.pbwiki.com/Namespaces</a><br><a href="http://gulik.pbwiki.com/Packages">http://gulik.pbwiki.com/Packages</a><br>
<br>I'm now writing tests and fixing up bugs in the core code. An alpha release will be made "soon".<br><br>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.<br>
<br>Gulik.<br><br clear="all"><br>-- <br><a href="http://people.squeakfoundation.org/person/mikevdg">http://people.squeakfoundation.org/person/mikevdg</a><br><a href="http://gulik.pbwiki.com/">http://gulik.pbwiki.com/</a>