I deprecated this method because it was not clean and there were no senders in the core. If this method is used, we should re-implement it. You cannot just use the super implementation. Method dictionaries internally include nil key/values just like Dictionaries do but MethodDictionary is implemented differently than Dictionary (its a variable subclass and the array contains values whereas the indexable part contains the keys). Adrian On May 28, 2009, at 12:30 , Stéphane Ducasse wrote:
I really do not know from where this method is coming from. Scary. We will have to improve our tracability
Stef
On May 28, 2009, at 11:25 AM, Romain Robbes wrote:
in Pharo 10318
On May 28, 2009, at 11:12 AM, Stéphane Ducasse wrote:
in which image?
Stef
On May 28, 2009, at 10:48 AM, Romain Robbes wrote:
Each time methodDictionary >> #do: is invoked, I get a warning. Worse, if warnings are disabled, it will not do anything, which sounds error-prone.
Why not just removing the method and use the implementation in Dictionary?
Romain
-- Romain Robbes http://www.inf.unisi.ch/phd/robbes
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Romain Robbes http://www.inf.unisi.ch/phd/robbes
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project