On Thu, Apr 10, 2008 at 2:51 PM, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote:
> 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. And I might add that this only way should be all down to the VM/Core level. For example, things like non-interruptible channels, and especially that evil, evil, evil STDIN that can't be interrupted no matter how many tricks are trown at it... Once you started read() on it, there is no way to get away from it... Thanks, --Vladimir --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
