TaskIT has a feature named StickyReference, for that propouse, is not trivial at all, because when you fork you are using a block that has a reference to a context. In the end even if your variable is nil, your process is being pointed by the context.
What i did in TaskIT is to have a witness object, that mixed with a ghost proxy (the one you will be pointing) can do the magic. If what you want in your process variable is not really a reference to the process or if you have enough with a partial proxy based in DNU, things can go easier, you just need to register that third object into the weak resgistry. If you check out taskit commit 20 you will find a mechanism based in a DNU based proxy. If you checkout the last stable version you will find the witness/ghost proxy based one. In any case, look for the method asStickyReference. It will lead you straight to the mechanism. Gofer new smalltalkhubUser: 'CAR' project: 'TaskIT'; configuration; load. (#ConfigurationOfTaskIT asClass project version: #stable) load: 'full' 2014-08-05 11:22 GMT+02:00 Udo Schneider <udo.schnei...@homeaddress.de>: > On 04.08.2014 21:35, stepharo wrote:> We should write a chapter on > finalization but since I do not know it > > > well (and I forget)... > > igor will answer you. > > > > Stef > > I found "the" bug. It seems it's a side effect of finalization, > WeakRegistry and cyclic references. I'll write a TestCase for that. > > Thanks, > > Udo > > > > >
