Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
According to Goetz in his book JCIP :
Because each thread has its own interruption policy , you should not interrupt a thread unless you know what interruption means to that thread .
Why did the Java language provide a public interrupt () method then ?Is this a design flaw? Who or what is supposed to interrupt a thread then ?
What he means is that if you don’t know what a thread does and how it works, you should not interrupt it. Since all threads can be interrupted, it is logical to have an
interrupt()method in classThread.You could ask the same thing for many other methods that can do “harm” when executed at the wrong place. The methods are the tools, and the programmer must use these tools wisely in order to create a program that works correctly.