[Pharo-project] SmalltalkImage vs SystemDictionary
Hi, I have a doubt ... why in Pharo 1.0 Smalltalk class == SystemDictionary and in Pharo 1.1 Smalltalk class == SmalltalkImage? Looking at the issue tracker (thanks Carla): We should make - Smalltalk pointing to SmalltalkImage current - have SystemDictionary only having classbindings management. and Smalltalk globals pointing to SystemDictionary instance. This way we finish the refactoring started long time ago. We should have a look at the way this was done in Squeak so that we get the same compatible for now solution. What's involved in *the refactoring started long time ago* and what's the motivation for it? Cheers -- Germán Leiva LeivaGerman@gmail.com
On Jun 7, 2010, at 1:32 AM, Germán Leiva wrote:
Hi,
I have a doubt ...
why in Pharo 1.0
Smalltalk class == SystemDictionary
and in Pharo 1.1
Smalltalk class == SmalltalkImage?
Yes this is normal now Smalltalk globals class == SystemDictionary
Looking at the issue tracker (thanks Carla): We should make
- Smalltalk pointing to SmalltalkImage current - have SystemDictionary only having classbindings management. and Smalltalk globals pointing to SystemDictionary instance.
this is done. which entry is that?
This way we finish the refactoring started long time ago. We should have a look at the way this was done in Squeak so that we get the same compatible for now solution.
What's involved in the refactoring started long time ago and what's the motivation for it?
Cheers -- Germán Leiva LeivaGerman@gmail.com _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
I expected that but what's the reason behind that change? The entry is http://code.google.com/p/pharo/issues/detail?id=2136 2010/6/7 Stéphane Ducasse <stephane.ducasse@inria.fr>
On Jun 7, 2010, at 1:32 AM, Germán Leiva wrote:
Hi,
I have a doubt ...
why in Pharo 1.0
Smalltalk class == SystemDictionary
and in Pharo 1.1
Smalltalk class == SmalltalkImage?
Yes this is normal
now Smalltalk globals class == SystemDictionary
Looking at the issue tracker (thanks Carla): We should make
- Smalltalk pointing to SmalltalkImage current - have SystemDictionary only having classbindings management. and Smalltalk globals pointing to SystemDictionary instance.
this is done. which entry is that?
This way we finish the refactoring started long time ago. We should have a look at the way this was done in Squeak so that we get
the same
compatible for now solution.
What's involved in the refactoring started long time ago and what's the motivation for it?
Cheers -- Germán Leiva LeivaGerman@gmail.com _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Germán Leiva LeivaGerman@gmail.com
Search in squeak-dev archive around 14 July 2009 [squeak-dev] Smalltalk vs SmalltalkImage current woes Also in February and March 2010 in squeak-devand Pharo mailing lists. Long, several month span, multithreaded discussions... As I said before, it would be good to have a rationale summarized in a wiki or somehere. Nicolas 2010/6/7 Germán Leiva <leivagerman@gmail.com>:
I expected that but what's the reason behind that change?
The entry is http://code.google.com/p/pharo/issues/detail?id=2136 2010/6/7 Stéphane Ducasse <stephane.ducasse@inria.fr>
On Jun 7, 2010, at 1:32 AM, Germán Leiva wrote:
Hi,
I have a doubt ...
why in Pharo 1.0
Smalltalk class == SystemDictionary
and in Pharo 1.1
Smalltalk class == SmalltalkImage?
Yes this is normal
now Smalltalk globals class == SystemDictionary
 Looking at the issue tracker (thanks Carla): We should make
- Smalltalk pointing to SmalltalkImage current - have SystemDictionary only having classbindings management. and Smalltalk globals pointing to SystemDictionary instance.
this is done. which entry is that?
This way we finish the refactoring started long time ago. We should have a look at the way this was done in Squeak so that we get the same compatible for now solution.
What's involved in the refactoring started long time ago and what's the motivation for it?
Cheers -- Germán Leiva LeivaGerman@gmail.com _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Germán Leiva LeivaGerman@gmail.com
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
To separate the namespace (SmalltalkDictionary) from all the image related tasks (SmalltalkImage). On Monday, June 7, 2010, Germán Leiva <leivagerman@gmail.com> wrote:
I expected that but what's the reason behind that change?
The entry is http://code.google.com/p/pharo/issues/detail?id=2136
2010/6/7 Stéphane Ducasse <stephane.ducasse@inria.fr>
On Jun 7, 2010, at 1:32 AM, Germán Leiva wrote:
Hi,
I have a doubt ...
why in Pharo 1.0
Smalltalk class == SystemDictionary
and in Pharo 1.1
Smalltalk class == SmalltalkImage?
Yes this is normal
now Smalltalk globals class == SystemDictionary
 Looking at the issue tracker (thanks Carla): We should make
- Smalltalk pointing to SmalltalkImage current - have SystemDictionary only having classbindings management. and Smalltalk globals pointing to SystemDictionary instance.
this is done. which entry is that?
This way we finish the refactoring started long time ago. We should have a look at the way this was done in Squeak so that we get the same compatible for now solution.
What's involved in the refactoring started long time ago and what's the motivation for it?
Cheers -- Germán Leiva LeivaGerman@gmail.com _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Germán Leiva LeivaGerman@gmail.com
-- Lukas Renggli www.lukas-renggli.ch
2010/6/7 Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> 2010/6/7 Lukas Renggli <renggli@gmail.com> Thanks for the info. Cheers 2010/6/7 Lukas Renggli <renggli@gmail.com>
To separate the namespace (SmalltalkDictionary) from all the image related tasks (SmalltalkImage).
On Monday, June 7, 2010, Germán Leiva <leivagerman@gmail.com> wrote:
I expected that but what's the reason behind that change?
The entry is http://code.google.com/p/pharo/issues/detail?id=2136
2010/6/7 Stéphane Ducasse <stephane.ducasse@inria.fr>
On Jun 7, 2010, at 1:32 AM, Germán Leiva wrote:
Hi,
I have a doubt ...
why in Pharo 1.0
Smalltalk class == SystemDictionary
and in Pharo 1.1
Smalltalk class == SmalltalkImage?
Yes this is normal
now Smalltalk globals class == SystemDictionary
Looking at the issue tracker (thanks Carla): We should make
- Smalltalk pointing to SmalltalkImage current - have SystemDictionary only having classbindings management. and Smalltalk globals pointing to SystemDictionary instance.
this is done. which entry is that?
This way we finish the refactoring started long time ago. We should have a look at the way this was done in Squeak so that we get
the same
compatible for now solution.
What's involved in the refactoring started long time ago and what's the motivation for it?
Cheers -- Germán Leiva LeivaGerman@gmail.com _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Germán Leiva LeivaGerman@gmail.com
-- Lukas Renggli www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Germán Leiva LeivaGerman@gmail.com
participants (4)
-
Germán Leiva -
Lukas Renggli -
Nicolas Cellier -
Stéphane Ducasse