I am in the process of porting my code to 6.0, and I found that I had to tweak the #next method in SmartRefStream in order to load properly some morphs that were serialized from a 5.1 image.
I had to add four calls to #rehash (see attached code).
Would that be something useful to have, or am I (again) missing something?
Stef
These discussions might be related:
http://lists.squeakfoundation.org/pipermail/squeak-dev/2021-November/217225.... http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-February/218957....
Am So., 24. Juli 2022 um 11:17 Uhr schrieb Stéphane Rollandin < lecteur@zogotounga.net>:
I am in the process of porting my code to 6.0, and I found that I had to tweak the #next method in SmartRefStream in order to load properly some morphs that were serialized from a 5.1 image.
I had to add four calls to #rehash (see attached code).
Would that be something useful to have, or am I (again) missing something?
Stef
Hmm... nothing would break if we do "too much" #rehash when loading objects via SmartRefStream, right? Hmm... well, except for performance...
I think that those #rehash calls should be added to #next bc. the results depend on the platform and are not intrinsic to the object to be loaded.
+1
Best, Marcel Am 24.07.2022 11:24:10 schrieb Jakob Reschke jakres+squeak@gmail.com: These discussions might be related:
http://lists.squeakfoundation.org/pipermail/squeak-dev/2021-November/217225.... [http://lists.squeakfoundation.org/pipermail/squeak-dev/2021-November/217225....]
http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-February/218957.... [http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-February/218957....]
Am So., 24. Juli 2022 um 11:17 Uhr schrieb Stéphane Rollandin <lecteur@zogotounga.net [mailto:lecteur@zogotounga.net]>:
I am in the process of porting my code to 6.0, and I found that I had to tweak the #next method in SmartRefStream in order to load properly some morphs that were serialized from a 5.1 image.
I had to add four calls to #rehash (see attached code).
Would that be something useful to have, or am I (again) missing something?
Stef
Ha. Looks like that #rehash does better fit in Object >> #readDataFrom:size:. See Kernel-mt.1526 and System-mt.1424. SqueakMap Catalog should update again fine in Trunk again. :-)
Best, Marcel Am 25.07.2022 12:35:59 schrieb Marcel Taeumel marcel.taeumel@hpi.de: Hmm... nothing would break if we do "too much" #rehash when loading objects via SmartRefStream, right? Hmm... well, except for performance...
I think that those #rehash calls should be added to #next bc. the results depend on the platform and are not intrinsic to the object to be loaded.
+1
Best, Marcel Am 24.07.2022 11:24:10 schrieb Jakob Reschke jakres+squeak@gmail.com: These discussions might be related:
http://lists.squeakfoundation.org/pipermail/squeak-dev/2021-November/217225.... [http://lists.squeakfoundation.org/pipermail/squeak-dev/2021-November/217225....]
http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-February/218957.... [http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-February/218957....]
Am So., 24. Juli 2022 um 11:17 Uhr schrieb Stéphane Rollandin <lecteur@zogotounga.net [mailto:lecteur@zogotounga.net]>:
I am in the process of porting my code to 6.0, and I found that I had to tweak the #next method in SmartRefStream in order to load properly some morphs that were serialized from a 5.1 image.
I had to add four calls to #rehash (see attached code).
Would that be something useful to have, or am I (again) missing something?
Stef
squeak-dev@lists.squeakfoundation.org
-
Jakob Reschke -
Marcel Taeumel -
Stéphane Rollandin