cool tristan if you have code we will integrate it in 1.2 :) Open a bug entry and put code there. Stef On May 11, 2010, at 11:28 AM, Marcus Denker wrote:
On May 11, 2010, at 11:20 AM, Tristan Bourgois wrote:
I understand what you said. But I think keyAtValue: is not pertinent. In the case where there are more than one same values, you can't know which value is selected.
I should say that replace keyAtValue: by keysAtValue: because, I think, it's more pertinent.
And clients that want to use the back-mapping can just do
(myDict keysAtValue: 'hello') first.
This would make the problem explicit. *and* they could even than add an assert to make sure that the mapping does not degenerate.
I cleaned ServerDirectory a little: http://code.google.com/p/pharo/issues/detail?id=2408
So there is just Encoder left. Which will disappear in 1.2 anyway.
So yes, we could do that.
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project