Den 11. okt. 2010 kl. 22:17 skrev Igor Stasenko siguc...@gmail.com:
Also, i used #ensure: and #ifCurtailed: but i tend to forget where
they are applicable and how.
So, little help in this regard will be wellcome.
Ensure: block always execute. IfCurtailed blocks only run if an error is
On Oct 11, 2010, at 10:17 18PM, Igor Stasenko wrote:
On 11 October 2010 22:49, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
The most important words in there are critical section. Carry on :)
Oh, please. This is not too hard to code.
My mind rolling around following choice(s)
On 12 October 2010 14:25, Henrik Johansen henrik.s.johan...@veloxit.no wrote:
On Oct 11, 2010, at 10:17 18PM, Igor Stasenko wrote:
On 11 October 2010 22:49, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
The most important words in there are critical section. Carry on :)
Oh, please.
On Oct 12, 2010, at 2:00 42PM, Igor Stasenko wrote:
On 12 October 2010 14:25, Henrik Johansen henrik.s.johan...@veloxit.no
wrote:
On Oct 11, 2010, at 10:17 18PM, Igor Stasenko wrote:
On 11 October 2010 22:49, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
The most important
On 12 October 2010 15:33, Henrik Johansen henrik.s.johan...@veloxit.no wrote:
On Oct 12, 2010, at 2:00 42PM, Igor Stasenko wrote:
On 12 October 2010 14:25, Henrik Johansen henrik.s.johan...@veloxit.no
wrote:
On Oct 11, 2010, at 10:17 18PM, Igor Stasenko wrote:
On 11 October 2010 22:49,
On 11 October 2010 14:40, Igor Stasenko siguc...@gmail.com wrote:
Hello,
here a situation, with which we can deal in more safer manner:
Suppose you have a weak registry, populated by different objects and
their executors.
Now, when some of them died, a weak registry performs finalization.
On Mon, 11 Oct 2010, Igor Stasenko wrote:
Hello,
here a situation, with which we can deal in more safer manner:
Suppose you have a weak registry, populated by different objects and
their executors.
Now, when some of them died, a weak registry performs finalization.
The potential danger is ,
[pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Levente Uzonyi
[le...@elte.hu]
Sent: Monday, October 11, 2010 10:24 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Another finalization concern: error handling
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Levente
On 11 October 2010 17:24, Levente Uzonyi le...@elte.hu wrote:
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Levente,
A similar discussion arose around Dolphin's event (#trigger*) mechanism.
My recollection is that it was not fully addressed due to performance
concerns. Forking and error
-boun...@lists.gforge.inria.fr] On Behalf Of Levente Uzonyi
[le...@elte.hu]
Sent: Monday, October 11, 2010 10:24 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Another finalization concern: error handling
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Levente,
A similar
On Mon, 11 Oct 2010, Igor Stasenko wrote:
On 11 October 2010 17:24, Levente Uzonyi le...@elte.hu wrote:
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Levente,
A similar discussion arose around Dolphin's event (#trigger*) mechanism.
My recollection is that it was not fully addressed due to
-project] Another finalization concern: error handling
On 11 October 2010 17:24, Levente Uzonyi le...@elte.hu wrote:
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Levente,
A similar discussion arose around Dolphin's event (#trigger*) mechanism.
My recollection is that it was not fully
On 11 October 2010 17:34, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Levente,
Ok, but just because the system saves us at the last instant does not mean
that we should be going out of our way to multiply free external resources.
Files are well known to the vm; other things (GSL
[pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Levente Uzonyi
[le...@elte.hu]
Sent: Monday, October 11, 2010 10:59 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Another finalization concern: error handling
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Levente
Argh
ObjectFinalizerfinalize
Finalize the resource associated with the receiver. This message
should only be sent during the finalization process. There is NO
garantuee that the resource associated with the receiver hasn't been
free'd before so take care that you don't run into
On Oct 11, 2010, at 4:10 13PM, Schwab,Wilhelm K wrote:
I am far more worried about having multiple executors per object (when did
p=malloc();free(p);free(p);free(p) become good style?) than I am about
getting the finalizer process itself completely robust at this point.
Bill
I fail to
, 2010 11:23 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Another finalization concern: error handling
On Oct 11, 2010, at 4:10 13PM, Schwab,Wilhelm K wrote:
I am far more worried about having multiple executors per object (when did
p=malloc();free(p);free(p);free(p
Meanwhile, i'll try to implement two test cases for WeakRegistryTest.
One, should cover following:
coll := OrderedCollection new.
obj := Object new.
wrapper := WeakArray with: obj.
coll add: wrapper.
obj toFinalizeSend: #remove: to: coll with: wrapper.
obj toFinalizeSend: #remove: to: coll
...@lists.gforge.inria.fr
[pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Henrik Johansen
[henrik.s.johan...@veloxit.no]
Sent: Monday, October 11, 2010 11:23 AM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Another finalization concern: error handling
On Oct 11, 2010, at 4:10 13PM
@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Another finalization concern: error handling
On Mon, 11 Oct 2010, Schwab,Wilhelm K wrote:
Henry,
Ok, what valid use of multiple executors have I missed?
I described it earlier how the AXAnnouncements project uses this feature.
Levente
Bill
] On Behalf Of Igor Stasenko
[siguc...@gmail.com]
Sent: Monday, October 11, 2010 12:14 PM
To: Pharo-project@lists.gforge.inria.fr; The general-purpose Squeak
developers list
Subject: Re: [Pharo-project] Another finalization concern: error handling
Meanwhile, i'll try to implement two test cases
-project-boun...@lists.gforge.inria.fr] On Behalf Of Igor Stasenko
[siguc...@gmail.com]
Sent: Monday, October 11, 2010 12:14 PM
To: Pharo-project@lists.gforge.inria.fr; The general-purpose Squeak
developers list
Subject: Re: [Pharo-project] Another finalization concern: error handling
, 2010 1:02 PM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Another finalization concern: error handling
On 11 October 2010 19:28, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
The Dolphin approach is to restart any of the finalizer, main, timer, idler
threads (I
On 11 October 2010 21:07, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
As a friend here: when did I say I'd remove all? Remove and process one at a
time. I will admit to having a bias toward doing this with a single executor
per object, but even if multiples turn out to have value
On Mon, 11 Oct 2010, Igor Stasenko wrote:
On 11 October 2010 21:07, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
As a friend here: when did I say I'd remove all? Remove and process one at a
time. I will admit to having a bias toward doing this with a single executor
per object, but
, 2010 2:36 PM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Another finalization concern: error handling
On 11 October 2010 21:07, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
As a friend here: when did I say I'd remove all? Remove and process one at a
time. I
On 11 October 2010 22:49, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
The most important words in there are critical section. Carry on :)
Oh, please. This is not too hard to code.
My mind rolling around following choice(s) (there may be others i don't see).
What would be a proper
-project-boun...@lists.gforge.inria.fr] On Behalf Of Igor Stasenko
[siguc...@gmail.com]
Sent: Monday, October 11, 2010 4:17 PM
To: Pharo-project@lists.gforge.inria.fr; The general-purpose Squeak
developers list
Subject: Re: [Pharo-project] Another finalization concern: error handling
On 11
...@gmail.com]
Sent: Monday, October 11, 2010 6:35 PM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] Another finalization concern: error handling
On 12 October 2010 00:32, Schwab,Wilhelm K bsch...@anest.ufl.edu wrote:
Sig,
How hard it is or isn't is not nearly as important as your
29 matches
Mail list logo
