> david
>
> I would really like to continue the cleaning of SystemDictionary
> because I do not like the current state of affair.
>
> Now we can either have a namespace class (with only namespace behavior)
both
> and a imageManagement class
>
> Now we could have one variable Smalltalk to point to either of it.
them :)
> but we will need another name.
> Now the point behind the current (which I do not like but live with it is
> that)
> it would be cool to be able to do from my image some query into your image).
> This was about thinking about that that SmalltalkImage current got birth.
>
> Now I would love to get some discussions about a way to
> - have a class management class = SystemDictionary but with clean
> contents and cool name => namespace?
> (which often people confused with having namespace at the language
> level and it not part of the proposal
> don't open the box please)
> - have a cool abstraction over image housekeeping
> - a cool abstraction about vm information
>
> so if you have ideas please let me know.
>
> Stef
>
>
> On Jan 4, 2010, at 9:16 PM, David T. Lewis wrote:
>
>> On Mon, Jan 04, 2010 at 07:09:01PM +0100, Laval Jannik wrote:
>>> Hi,
>>>
>>> I understand your comments,
>>> So:
>>> - i will put word size a class var,
>>> - this class var will be modify only by systemTracer
>>>
>>> Now I have a question:
>>> Why using Smalltalk wordSize whereas the vm parameter is getting by
>>> SmalltalkImage current ?
>>
>> Hi Jannik,
>>
>> Different people may answer this question in different ways, because it
>> is a matter of style and personal opinion. But it may help to know that
>> earlier versions of Squeak had the vm parameter query in SystemDictionary
>> ("Smalltalk") rather than in SmalltalkImage. This was moved as part of
>> a larger effort to reorganize SystemDictionary, which is a rather large
>> class that has accumulated many functions over the years.
>>
>> As matter of function, it makes no difference either way. The part that
>> is subject to opinion is whether it makes more sense for a person to
>> say "Smalltalk wordSize" to refer to the size of a word in the object
>> memory, or whether "SmalltalkImage current wordSize" is more meaningful.
>>
>> FWIW, my own opinion is that neither one is right, but "Smalltalk wordSize"
>> is easier to remember. But no matter what approach is taken, you will be able
>> to find someone who does not agree, so you should form your own opinion ;-)
>>
>> HTH,
>>
>> Dave
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
