[Bug 64] Thread.interrupt() and co. unreliable/dangerous/buggy

[email protected]
Newsgroups gmane.comp.java.vm.sablevm.bugs
Message-ID <[email protected]>
http://sablevm.org/bugs/show_bug.cgi?id=64

[email protected] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|[email protected]    |[email protected]



------- Additional Comments From [email protected]  2004-09-28 00:43 -------
These 3 functions have no need to be JNI functions, because the I/O already
takes place in an JNI code, so basically we would only need to call these 3
JVM functions.  I do not think we have any existing case of such calls.
I am not sure this is entirely good idea to have such calls, too.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.