The interrupt is often used for notifying of shutdown, in which case you should probably just rethrow the exception. It can also be used by a timeout task to notify another that its time to complete a task has expired.
You might try to remove the catch and wonder why the compiler complains. Java wants to prepare for the possibility that the sleep may be prematurely awakened by some wandering Prince Charming. It is not nearly as sure as you are that it can’t happen.
You can even put main event-processing thread to sleep, but if you do, no events will be processed; buttons will be dead.
You don’t need to implement Runnable to use sleep.
It is best to use wait/notify to coordinate threads, not have them sleep and wake up and check then sleep again. There is no guarantee Threads won’t sleep longer than you requested.
See the warning under Gotchas:Threads on why a sleeping task may never waken if somebody fiddles with the system clock setting while your thread is asleep.
available on the web at:
optional Replicator mirror
Please email your feedback for publication, letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording, broken/redirected link reports, suggestions to improve this page or comments to Roedy Green : . If you want your message, your name or email kept confidential, not considered for public posting, please explicitly specify that. Unless you state otherwise, I will treat your message as a letter to the editor that I may or may not publish in the feedback section. After that, it will be too late to retract it. If you disagree with something I said, especially when sending an ad-hominem attack, a rant composed mainly of obscenities or a death threat, please quote the offending passage and cite the web page where you found it, tell me why you think it is wrong, and, if possible, provide some supporting evidence. I can’t very well fix erroneous or ambiguous text if I can’t find it.
Your face IP:[184.108.40.206]
|Feedback||You are visitor number 102,042.|