On 3/29/2010 3:36 PM, Nicolas Cellier wrote:
Yup. Good call. The problem is deeper though. What we did was change the hash function and as a result all the hashed collections that are exchanged between images with different hash functions will fail.
A *perfect* example why ImageSegments are not a reliable long-term storage btw. The bits are all the same but the interpretation of the bits has changed (identityHash vs. scaledIdentityHash). Storing bits without behaviors only works if you have tight control over both ends (like in Croquet where we ensure identical code bases).
Cheers, - Andreas
2010/3/30 Andreas Raab andreas.raab@gmx.de:
On 3/29/2010 3:36 PM, Nicolas Cellier wrote:
Yup. Good call. The problem is deeper though. What we did was change the hash function and as a result all the hashed collections that are exchanged between images with different hash functions will fail.
A *perfect* example why ImageSegments are not a reliable long-term storage btw. The bits are all the same but the interpretation of the bits has changed (identityHash vs. scaledIdentityHash). Storing bits without behaviors only works if you have tight control over both ends (like in Croquet where we ensure identical code bases).
Cheers, - Andreas
Yes, that's why I call this workaround rather than fix. It's fragile.
Nicolas
squeak-dev@lists.squeakfoundation.org