From what I understand:

        -       on: do: register the block context as the receiver to kick in 
the block evaluation
                => weak registration is then not weak anymore

        - there was an old LegacyRegistrationMechanism that works (fallback for 
old VM that do not 
        have the right way of managing weak structure) and the 
LegacyRegistration got some 
        on:do: and grew grew grew.

Stef



On Sep 19, 2013, at 5:30 PM, Goubier Thierry <[email protected]> wrote:

> 
> 
> Le 19/09/2013 17:20, Esteban Lorenzano a écrit :
>> Hi,
>> 
>> I just submitted and integrated a fix for the leak problem.
>> That should fix the problem we are having in Pharo3... now we need to work 
>> on a backport for Pharo2... any takers? :)
> 
> I need some explanations :)
> 
> Thierry
> 
>> Esteban
>> 
>> 
> 
> -- 
> Thierry Goubier
> CEA list
> Laboratoire des Fondations des Systèmes Temps Réel Embarqués
> 91191 Gif sur Yvette Cedex
> France
> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
> 


Reply via email to