I don't think there's something to fix.

You cannot 'extend' classes belonging to other package in any other way

than adding extension methods.

Allowing extension of ivars or any other vars by foreign package

is road to nowhere.

I would not like if shape of my kernel classes depends on what packages i load

or in what order i loaded them.

To me it is clear that if one needs to add/remove/modify instance variables

of some class, those changes should belong to the package containing that class,
not some random package.

On 30 October 2013 19:15, St��phane Ducasse <stephane.ducasse@inria.fr> wrote:

Ok in fact
Gisela forked the AST-Core package to be able to load a new version with the instance variables.
Because there is no way to say that a class definition modification is attached to a given package.

Stef

> Apparently the problem is that gisela is adding instance variable to a class that is not in the Flamel package.
> So it was working before but not anymore.
>
> Stef
>
>
>
>> Hi guys
>>
>> we are losing instance variables addition when loading a package.
>> Here is the example:
>>
>> �� Gofer new
>> �� url: 'http://smalltalkhub.com/mc/gisela/Flamel/main';
>> �� version: �� 'Flamel-GiselaDecuzzi.94';
>> �� load
>>
>> Normally RBProgramNode should have three new instance variables and not this is not the case.
>> Is it a known bug?
>>
>> Stef
>
>

--
Best regards,
Igor Stasenko.