Re: Thread Cancelation
Re: Thread Cancelation
- Subject: Re: Thread Cancelation
- From: Clark Cox <email@hidden>
- Date: Fri, 29 Oct 2004 14:13:21 -0400
On Fri, 29 Oct 2004 19:01:17 +0100, Benjohn <email@hidden> wrote:
>
>
We've just started porting our .Net application over to OS X.
>
>
We have a thread abstraction which assumes it is possible to cancel a
>
thread. If a thread is sleeping, or waiting on a semaphore or mutex, it
>
will gracefully terminate when asked. Otherwise, the thread will cancel
>
itself when it is prepared to do so.
>
>
In trying to implement our thread abstraction in OS X, we're
>
encountering "some trouble". From what we've found so far, it seems
>
that neither NSThread, nor the p_thread implementation in OS X, will
>
meet our requirements.
>
>
I'd appreciate it if someone could confirm that the thread
>
implementations in OS X do not allow cancelling of a thread that is
>
waiting on a mutex or semaphore, or is sleeping; I'm reluctant to
>
undertake a considerable rewrite, or tender my resignation, if it is
>
not entirely necessary.
On most threading implementations, canceling a thread is a bad idea.
If a thread is sleeping or waiting on a mutex, etc, what, exactly do
you expect to happen? What happens to any memory that code in that
thread allocated? What happens to resources that that thread my have a
lock on? What happens to objects that still have positive retain
counts?
--
Clark S. Cox III
email@hidden
http://www.livejournal.com/users/clarkcox3/
http://homepage.mac.com/clarkcox3/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden