<br><br><div><span class="gmail_quote">On 2/19/07, <b class="gmail_sendername">Alan Lovejoy</b> <<a href="mailto:squeak-dev.sourcery@forum-mail.net">squeak-dev.sourcery@forum-mail.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div><span><font face="Arial" size="2">Michael,</font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">I don't understand
your issue. You say you want to "get Namespaces out of an image."
What, precisely, do you mean by that? What's the connection between having
namespaces and needing to change the location-of-record for method
sources? Shouldn't those two issues be indepedent of each
other?</font></span></div></div></blockquote><div><br>I have an image. In that image is a Namespace. I need to get that Namespace and the source for the classes in that Namespace out of that image and in to another image somehow - usually done using
e.g. Monticello, filings stuff out, etc.<br><br>The format for SqueakV9.sources, squeak.changes, changesets and file-outs will have to change a bit if they were to support Namespaces. Rather than changing the format, another option is to chuck everything out the window and use a different system, such as keeping the source code and version information in the image as Text objects. I'm just wanting people's opinions on the technical merits of the options I mentioned in the root of this thread.
<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div><span><font face="Arial" size="2">Namespaces should do
the following: </font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span><font face="Arial" size="2">
1) **Transparently** replace "shared pool dictionaries"; and</font></span></div>
<div><span><font face="Arial" size="2"></font></span> </div>
<div><span> <font face="Arial" size="2">2) Enable "the same global name" to refer to different values in the
context of different classes (or perhaps even different methods) without
requiring any change to existing method sources or to the syntax of variable
names (Namespaces should be completely orthogonal to syntactical issues, such as
whether to enable "MyPackage.MyClass" or "MyPackage::MyClass" or
"MyPackage#MyClass" as new syntax for referring to variables in specific
namespaces.)</font></span></div></div></blockquote><div><br>Ahh... yea... they do all that now. I haven't tested it yet though.<br><br>Michael. <br></div><br></div><br>