[Metakit] MkPy hash view problems

[Pat Thoyts]

-----BEGIN PGP SIGNED MESSAGE-----

Lars Heuer wrote:
| Hi Brian,
|
|
|>You can't trust the indexes returned from hashed or ordered views,
|>they simply aren't correct.  The index returned is the index that
|>*would* have been returned if the hash or ordering wasn't applied.
|>This probably just affects the python wrappers, but I don't know.
|
|
| Maybe it would be worth to put a note on this at the Metakit/Python
| webpage.
|
| Can somebody verify that the mentioned problem does _not_ exist
| in other Metakit environments?

No - this occurs when using C++ too. It is necessary to find the new index, the
returned value is useless if there is any ordering/hashing going on.

Pat Thoyts
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows XP)

iQCVAwUBQwaDfmB90JXwhOSJAQEJTQQAh8tvq3Xdk0cOD8Fqkbb/S0Cbqita+EUW
4no0W7t7xv+iW8bl2Ybu6BuLXaTzzbRZSxiUvVNxoFYoIDhgU8xLVGmfqX3ar3mh
/+n1gqQQmdrAXGRKtdHanSMHC3wE9/ie9+zxKSUmpQ1/cby6bPmKJe5WMHaG4zsw
nVriHnyg3NU=
=9NAo
-----END PGP SIGNATURE-----