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 <[email protected]>

>
> 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
> > [email protected]
> > _______________________________________________
> > 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
>



-- 
Germán Leiva
[email protected]
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to