Re: [Pharo-project] WTF -> instVar called 'behaviors' in first slot

May 16, 2012


      any direct users of #instVarAt: maybe?

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

Re: [Pharo-project] WTF -> instVar called 'behaviors' in first slot

Camillo Bruni