[squeak-dev] SmartRefStream tweak?

Marcel Taeumel marcel.taeumel at hpi.de
Mon Jul 25 10:35:59 UTC 2022

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.


Am 24.07.2022 11:24:10 schrieb Jakob Reschke <jakres+squeak at gmail.com>:
These discussions might be related:

http://lists.squeakfoundation.org/pipermail/squeak-dev/2021-November/217225.html [http://lists.squeakfoundation.org/pipermail/squeak-dev/2021-November/217225.html]

http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-February/218957.html [http://lists.squeakfoundation.org/pipermail/squeak-dev/2022-February/218957.html]

Am So., 24. Juli 2022 um 11:17 Uhr schrieb Stéphane Rollandin <lecteur at zogotounga.net [mailto:lecteur at 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?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220725/3de4a349/attachment.html>

More information about the Squeak-dev mailing list