> It does not interrupt arbitrary code in any way. That would not be  
> safe,
> since locks could be held, resources could be left unresolved, and  
> so on.
>
> Long story short, checkpointing is the only way, since the target  
> thread
> must willingly "give up" in order for you to terminate its execution.

Out of interest: I've heard that Smalltalk and Lisp had - at least in  
some implementations - a safe way to interrupt arbitrary threads. Does  
anyone know anything about that or have some pointers?

I think safely interruptible threads would be really nice, in any  
environment. I do unterstand the reasons why Java doesn't have them,  
but I'm still curious.

I think it also might be nice to implement a Thread.kill(), one day.

Regards,
Martin

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "JVM 
Languages" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/jvm-languages?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to