|
![](/i/fill.gif) |
Warp wrote:
> Darren New <dne### [at] san rr com> wrote:
>> As for exiting a thread by forcing it to throw an exception, that makes
>> perfect sense from an implementation point of view.
>
> Usually threads are ended by exiting the function that was launched by
> the thread...
Exactly. So the thread equivalent of "exit()" usually throws an exception
that's generally outside the usual exception hierarchy, in order to unwind
the stack and cause the top-most function to exit without screwing up other
threads. And most thread libraries for languages with exceptions give you a
way to make that happen in some other thread.
--
Darren New, San Diego CA, USA (PST)
Serving Suggestion:
"Don't serve this any more. It's awful."
Post a reply to this message
|
![](/i/fill.gif) |