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.
> 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
> This can lead to subtle bugs in
> various situations that are very hard to debug. Furthermore consider
> that the code that shadows instance variables in unlikely to load into
> any other Smalltalk.
>
> 2) In various code bases I see an increasing number of unused
> temporary variables. Instead of just leaving them in there it would be
> nice if the compiler removed them right away.
http://code.google.com/p/pharo/issues/detail?id=2103
>
> Point 1 is a *major* annoyance, I already lost hours for that reason.
>
> Point 2 is not that important, as it has no intermediate consequences
> and can be deferred to code critics. I would need to write a new lint
> rule though.
>
> If I knew where these compiler changes were done, I would propose a
> fix for Pharo 1.0 and 1.1. Any pointers?
>
> 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
