Right. In which case what we need to do is recategorise the methods.
#alansTextPlusMorphbosfcebbmsopssrsggshtt0 belongs in *Morphic-Extras
because its mapped class, TextPlusMorph, is in that package, and so
on.

I can appreciate the cleverness of the hack, while being mildly
distressed at its fragility. But that just goes to show you that
serialising closures is hard.

frank

On 13 May 2013 18:22, Bob Arning <arning315 at comcast.net> wrote:
> They are used when reading a file containing a reference to a class which no
> longer exists. These methods map the old class to a new one. The selector is
> the name of the old class (first letter downshifted) followed by the first
> letter of the inst var names at the time that object was written to the
> file. See the #writeClassRename... methods for creation. See #mapClass: for
> usage.
>
> Cheers,
> Bob
>
>
>
> On 5/13/13 12:57 PM, Frank Shearar wrote:
>
> SmartRefStream has messages like
>
> * alansTextPlusMorphbosfcebbmsopssrsggshtt0
> * abstractStringx0
> * layoutMorphbosfcepbbochvimol0
> * layoutMorphbosfcepcbbochvimol0
>
> and many others. The timestamps go back a ways, some to 1998. Squeak
> 4.3 has them. Where'd they come from? More importantly, are they just
> junk that we can remove?
>
> frank
>
>
>
>
>
>