But marcus the problem is right now keyAtValue: is bogus. Did you see it?
On May 11, 2010, at 9:41 AM, Marcus Denker wrote: > Hi, > > I think one question one should always ask: Do I have a real need for the new > method? > > Sometimes it makes sense to add new API methods even outside of direct need. > Consistency is the most important reason to add something. > > So is there a direct need for your method? > > Marcus > > > > On May 10, 2010, at 4:36 PM, Tristan Bourgois wrote: > >> >> keyAtValue: returns one key of the value specified but if you have more time >> the same value the method return one key. >> An example: >> t:=Dictionary new. >> t at: 'toto' put: 4. >> t at: 'foo' put: 4. >> t keyAtValue:4. -> 'foo' >> >> So we can't recuperate all of the keys. I propose to create the methods >> keysAtValue: who return an Array with all the keys for this value. >> >> I'm not in Pharo very long time so I can not say if it can be useful so I am >> asking to you the question. >> >> Tristan Bourgois. >> -- >> View this message in context: >> http://forum.world.st/keyAtValue-keysAtValue-tp2165484p2165484.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
