[Pharo-dev] unloading Nautilus

Stéphane Ducasse stephane.ducasse at inria.fr
Wed Oct 2 14:14:46 EDT 2013


Ok 
I will check now I do not even understand why and how it is related.

Stef

> it's the inspector, not nautilus.
> 
> => InspectorNavigator >> pushHistory:
> 
> On 2013-10-02, at 19:20, Stéphane Ducasse <stephane.ducasse at inria.fr> wrote:
> 
>> When I try
>> 
>> (MCWorkingCopy forPackage: (MCPackage named: 'NautilusRefactoring')) unload
>> 
>> NautilusUI allInstances do: [ :inst | 
>> SystemAnnouncer uniqueInstance unsubscribe: inst].
>> Smalltalk garbageCollect.
>> 
>> (MCWorkingCopy forPackage: (MCPackage named: 'NautilusCommon')) unload.
>> (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload 
>> 
>> I get the attached system. I do not understand why SpecDebugger has something to do with navigationHistory.
>> 
>> Any idea?
>> I also think that we are not good at making sure what we load can be cleanly unloaded. Without that discipline we will never have 
>> a modular system.
>> 
>> Stef
>> 
>> 
>> <Screen Shot 2013-10-02 at 7.04.02 PM.pdf>
> 





More information about the Pharo-dev mailing list