Why does Squeak what it does when a method references a non-existing ivar?

Cees De Groot cdegroot at gmail.com
Sat Nov 12 11:54:44 UTC 2005


I understand the need for keeping consistency, but can't we come up
with something better than silently share a global? Why not point
these things to something that throws an error when actually
referenced?

On 11/12/05, Andreas Raab <andreas.raab at gmx.de> wrote:
> If you want to fix
> this problem you should deal with it when you remove the iVar (e.g., the
> browser should check if there are still references and put up a message
> set so you can fix them).
>
Yup. I'll check whether I can (find the time to) cook up such a patch.

> Also, keep in mind you can get to those vars by inspecting Undeclared
> and using "references to..." you can find where they are being used.
>
After cleaning them out, which you can find how to do by going through
the method finder... Oh well, I won't complain, i'll just add more
stuff to my QualityControl package ;)



More information about the Squeak-dev mailing list