I did the following check. We should really get rid of this compiler.
Yes, but somebody has to write a new compiler first. The one in the image is the only one that works.
So for Pharo we get simply for now issue Parser warningAllowed: true to get it to the "normal" behavior
That's Pharo 1.1?
In 1.0 =================
Parser warnUser
but we have the same silly broken pop up.
Yeah, but that is better than accidently shadowing variables.
we got 'Name is already defined.' so it seems that this is not the warning preference that are responsible of the problem.
You lost me. :-) Lukas
I will ask marcus if he remembers which compiler changes may have Stef
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli http://www.lukas-renggli.ch