On Wed, May 16, 2012 at 1:27 PM, Camillo Bruni <[email protected]>wrote:
> any direct users of #instVarAt: maybe? > > Yes. FLPackage is serialized by Fuel, so as any other object, Fuel will send #instVarAt: to trace all its instvars. But I guess that should not be a problem. > On 2012-05-16, at 12:45, Mariano Martinez Peck wrote: > > > Hi guys. Today we had something really strange with Pharo 2.0. We are > serializing FLPackage: > > > > Object subclass: #FLPackage > > instanceVariableNames: 'extensionMethods behaviors mustInitialize > preLoadActions postLoadActions additionalObjects' > > classVariableNames: 'MustInitializeByDefault' > > poolDictionaries: '' > > category: 'FuelPackageLoader' > > > > That definition, where 'extensionMethods' is before 'behaviors' it works > perfect. However, when just switching the oder to: > > > > Object subclass: #FLPackage > > instanceVariableNames: 'behaviors extensionMethods mustInitialize > preLoadActions postLoadActions additionalObjects' > > classVariableNames: 'MustInitializeByDefault' > > poolDictionaries: '' > > category: 'FuelPackageLoader' > > > > > > The serialization of PharoCore fails because a problem with a metaclass > of HTTPSocket. > > > > Any idea what can happen? > > > > thanks > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > -- Mariano http://marianopeck.wordpress.com
