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

would it not that the classBuilder use a different path and that it sort iv on some ways and not on the other ones.

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