Thanks lukas I think that we will have to have a look at the changes made to the compiler in 1.0. ;-/ I will wait that marcus shows up but indeed we should fix that
Stef >> Do you refer to the fact that we do not get this stupid pop-ups? >> there is preference for that I think. So we could set up by default. >> Did you see it? >> http://code.google.com/p/pharo/issues/detail?id=1224 >> >> Tell me if it helps you and sorry for the inconvenience incomplete progress >> is >> putting on you. > > I don't know why this was changed? Probably point 1 is an unintended > side-effect of point 2? > > I like the progress that Pharo 1.0 is doing. All in all it is a huge > progress every week. It is only this tiny detail that I find should be > undone :-) > >>> Before going to Pharo 1.0 final, could we please undo the compiler >>> changes that handle the temporary variables? >>> >>> 1) In various code bases I see an increasing number of temp variables >>> that shadow instance variables. >> >> Yes this can be annoying we should find a solution in 1.1. >> http://code.google.com/p/pharo/issues/detail?id=2102 > > I think this has to be changed as soon as possible, e.g. for Pharo 1.0 > final. If somebody pointed me to where this was changed I could even > assemble a fix. > > Point 2 could be a preference (or a lint rule). That doesn't hurry at > all and is fine for Pharo 1.1 (or later). > > Lukas > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > 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
