Hi Ralph--
I'm just getting into Spoon (hmm, I'm just learning to use Spoon, I'm getting stirred up with Spoon, ... there ought to be a good line here)...
Yeah, I like "getting a handle on Spoon". :)
Spoon currently still has the old system dictionary, but I'd like to remove it. I think we should just rewrite users of "Smalltalk at:" (probably in some automated fashion, both in situ and during method transfer). Instead of a system dictionary, I'd rather have some class take responsibility for each former non-class "global" variable, and use messages for access. Or just use shared pools for such variables. (Heh, shared pools is another topic that gets some people riled up. :)
The classes we can put in some cache collection that is known to the compiler, but it need not be keyed. Then each class has complete responsibility for its name, and we needn't worry about other objects having out-of-sync notions of any class names.
I don't think we need class or module namespaces in Spoon.
-C
Spoon currently still has the old system dictionary, but I'd like to remove it. I think we should just rewrite users of "Smalltalk at:" (probably in some automated fashion, both in situ and during method transfer). Instead of a system dictionary, I'd rather have some class take responsibility for each former non-class "global" variable, and use messages for access. Or just use shared pools for such variables. (Heh, shared pools is another topic that gets some people riled up. :)
Is the existing 'self class environment' not the palce to start?
Is the existing 'self class environment' not the palce to start?
Yes, 'self class environment' is not the place to start. :) (in my opinion)
I'd like to remove all that stuff, too.
-C
spoon@lists.squeakfoundation.org