Re: [Pharo-users] difficult to kill objects - pesky hanging pointersTo

On 7 September 2016 at 20:45, stepharo wrote: > And wht I learned is that we should do > > > ClassOfObjectsThatMustDie allInstances first become: nil > but really String new. > But why a two-way become and not a becomeForward?

Re: [Pharo-users] difficult to kill objects - pesky hanging pointersTo

And wht I learned is that we should do ClassOfObjectsThatMustDie allInstances first become: nil but really String new. Le 6/9/16 à 02:22, Ben Coman a écrit : Ohhh... nice... shiny... That is much easier to remember. Thanks Andres. cheers -ben On Tue, Sep 6, 2016 at 5:21 AM, Andres Valloud

Re: [Pharo-users] difficult to kill objects - pesky hanging pointersTo

Ohhh... nice... shiny... That is much easier to remember. Thanks Andres. cheers -ben On Tue, Sep 6, 2016 at 5:21 AM, Andres Valloud wrote: > So why doesn't two-way become: help, e.g. > > ClassOfObjectsThatMustDie allInstances first become: String new > > As

Re: [Pharo-users] difficult to kill objects - pesky hanging pointersTo

So why doesn't two-way become: help, e.g. ClassOfObjectsThatMustDie allInstances first become: String new As soon as that do-it unwinds there won't be any references to what the new string became (the new string wasn't referenced further), so... On 9/5/16 8:50 , Ben Coman wrote: Sometimes