Well, i understand than problem not is if exists the message or not, else than message is called by SmartRefStream class in some method.
Regards Stéphane Ducasse-2 wrote: > > But I'm not sure it was working. > Let us know if you need to have it back or which version. > > Stef > > On Sep 25, 2009, at 12:35 PM, Stéphane Ducasse wrote: > >> Yes it was removed. >> >> Stef >> >> On Sep 25, 2009, at 11:13 AM, nullPointer wrote: >> >>> >>> >>> When a object is serialized, a Morph for example , and the class of >>> that >>> morph change, when i try deserialize the morph i get the error does >>> ´nt not >>> understand #convertToCurrentVersion:refStream: >>> >>> I did see older images of Pharo and exists that method, defined in >>> Object >>> and Morph too. Seems than adapt the old class form to new version, if >>> changed. The caller of that message is the class SmartRefStream. >>> >>> My image is a Pharo BETA 10418. >>> >>> Regards >>> -- >>> View this message in context: >>> http://n2.nabble.com/Bug-don-t-found-convertToCurrentVersion-refStream-tp3711278p3711278.html >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [email protected] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- View this message in context: http://n2.nabble.com/Bug-don-t-found-convertToCurrentVersion-refStream-tp3711278p3712815.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
