2009/11/4 <csrabak@bol.com.br>:
Em 04/11/2009 17:53, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> escreveu:
Right. Â However, shouldn't the message about shadowing be issued when we accept the method in the browser?
Yes, but that would occur when adding a Trait to class definition... Or when adding an inst var to a traitified class definition In both case, you don't have method source under the browser scope, so it is hard to interact. I guess this was a (bad) reason motivating silent warnings.
 ???       Just      looking      the      first ArrayTest>>#testCopyReplaceAllWith1Occurence,  it has  a  temp named result and an inst var named result
 2009/11/4 Lukas Renggli :
First I thought this is  because temps in trait methods shadow the inst-vars of  the classes  that use these  traits (ouch!),  but it doesn't seem to be the case.  I don't understand either why we get these messages. Lukas 2009/11/4 Stéphane Ducasse :
Strange this is related to traits? Stef On Nov 4, 2009, at 5:17 PM, Lukas Renggli wrote:
When I recompile a Pharo image Compiler recompileAll I get 819 messages  complaining about shadowed variables, mostly but not only in the new collection tests. Does anybody knows why this happens? Lukas [819 messages snipped]
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project