[squeak-dev] EncoderForV3PlusClosures still the preferred bytecode set encoder class?

Fabio Niephaus lists at fniephaus.com
Tue Dec 15 14:55:35 UTC 2020

Hi all,

The latest Squeak trunk (6.0alpha-20097) is still using
EncoderForV3PlusClosures as the preferred bytecode set encoder class.
So new methods are still being compiled with it (not necessarily a
problem, because the VM can handle both V3 and Sista at the same

Is this something we've done on purpose or something we should fix?


More information about the Squeak-dev mailing list