May 11, 2010
9:15 a.m.
On May 11, 2010, at 11:13 AM, Marcus Denker wrote:
On May 11, 2010, at 10:35 AM, Stéphane Ducasse wrote:
But marcus the problem is right now keyAtValue: is bogus. Did you see it?
It does work when ypu know that there is only one value that is identical.
Than you can use it to map back and forth. (slowly one of them, of course).
If there are two values that are the same, the message does not make that much sense.
I guess this method is used for just the cases when the client needs a table for maping in both directions.
The only client in the Core image is ServerDirectory:
Ups. Missed Encoder>>tempNames. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.