Stay with the global Squeak! It is even better than Smalltalk. What is 
'Squeak' if not the image with which you are right now working? More 
people will intuitively understand what is meant, 'SmalltalkImage 
current' is confusing. There will be questions like: Is Smalltalk = 
Squeak?? Or: The current image is in the memory: Do I have direct 
access to that memory?? 

And if you do not like SmalltalkImage, well why not call it System? 
That name would be better suited for a class with broad administrative 
responsibility ( if I understand you correctly that you want to put 
more methods into it - which I would prefer :-).

Last but not least: Keep it simple. Small things accumulate to big
things. We want to have elegance - not a second VisualWorks.

Regards
Martin


ducasse <ducasse at iam.unibe.ch> wrote on 02.10.2003 16:15:13:
>
>Hi daniel
>
>I agree with you but why did you tell it before?  I spent more than 2 
>hours fixing all the SmalltalkImage uniqueInstance into Squeak.
>(I do not like SmalltalkImage because this is more than that you will 
>see when we will have all the GC related methods inside).
>
>Now I ready to change again but people should shout now!!!!!!!!!
>because I will do it twice. I raised the question before and got two 
>answers. so what.
>
>Stef
>
>
>
>On Jeudi, oct 2, 2003, at 15:45 Europe/Zurich, Daniel Vainsencher 
>wrote: 
>
>>
>> First, about the refactoring itself, and the responsibilities moved 
>> to SystemVersion and SmalltalkImage, I think the change is good. I 
>> want to raise some naming issues, though -
>>
>> IIUC, the new global Squeak is defined to reference SmalltalkImage's
>> sole instance. First, I'm not sure that's a good use for the name. 
>> The functions therein are esoteric for most people, and Squeak is a 
>> very non
>> specific name for it.
>>
>> Second, the code, change set comment and deprecation comments vary 
>> on whether to reference this instance as
>> - SmalltalkImage uniqueInstance
>> - SmalltalkImage current
>> - Squeak
>>
>> Whatever we pick, it better be consistent. I personally would 
>> prefer the
>> "current" variant. About using Squeak - I think Globals should be
>> reserved to commonly accessed concepts. SmalltalkImage doesn't seem 
>> to be one, so I'd be lazy about giving it the name. These things 
>> are easier
>> to give than to take away...
>>
>> Daniel