On 06.08.2014 02:36, Ben Coman wrote:
Is there a Fogbugz case to track it?
cheers -ben
There is now:
https://pharo.fogbugz.com/f/cases/13785/Cyclic-Referencing-self-prevents-an-object-from-being-finalized
CU,
Udo
Udo Schneider wrote:
On 05.08.2014 14:08, Udo Schneider wrote:
I also reduced the testcases to even show a (IMHO) faulty behavior w/o
any process at all. Simple references are sufficient.
I just created a small TestCase showing the (IHMO) faulty behavior. I
hope the intention is clear from the
On 05.08.2014 14:08, Udo Schneider wrote:
I also reduced the testcases to even show a (IMHO) faulty behavior w/o
any process at all. Simple references are sufficient.
I just created a small TestCase showing the (IHMO) faulty behavior. I
hope the intention is clear from the package/var names.
G
On 05.08.2014 12:10, Santiago Bragagnolo wrote:> 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
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 obje
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
We should write a chapter on finalization but since I do not know it
well (and I forget)...
igor will answer you.
Stef
On 2/8/14 13:16, Udo Schneider wrote:
All,
I just stumbled over something which thought was pretty easy - turned
out it isn't as easy as I thought or I'm simply ___ (fill
On 02.08.2014 15:33, Ben Coman wrote:
I don't know much about finalization of Weak constructs, but maybe an
alternative. I assume you have something like..
startProcess
["do stuff"] fork.
so how about...
startProcess
[ [
"do stuff"
myProcess = nil.
] whi
Udo Schneider wrote:
All,
I just stumbled over something which thought was pretty easy - turned
out it isn't as easy as I thought or I'm simply ___ (fill in
expression of choice like "too dumb", "blind", etc.)
I have an object which starts a background process to do it's job.
This objec
All,
I just stumbled over something which thought was pretty easy - turned
out it isn't as easy as I thought or I'm simply ___ (fill in
expression of choice like "too dumb", "blind", etc.)
I have an object which starts a background process to do it's job. This
object holds a reference to
> #beFinalizable, which doesn't seem to exist. I guess it was just an
example, but seems like it should be added, no?
Do you agree that #beFinalizable would be a nice addition? If so, I will
open an issue...
Igor Stasenko wrote
>> See NBExternalResourceManager class comment
So the point of usin
On 29 November 2013 07:21, Sean P. DeNigris wrote:
> I found the following list threads...
>
> http://forum.world.st/Finalization-question-td1300962.html mentions
> #beFinalizable, which doesn't seem to exist. I guess it was just an
> example,
> but seems like it should be added, no?
>
> In http:
I found the following list threads...
http://forum.world.st/Finalization-question-td1300962.html mentions
#beFinalizable, which doesn't seem to exist. I guess it was just an example,
but seems like it should be added, no?
In http://forum.world.st/object-finalization-td3771196.html Igor suggested
13 matches
Mail list logo
