Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!border3.nntp.ams.giganews.com!Xl.tags.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!local2.nntp.ams.giganews.com!nntp.bt.com!news.bt.com.POSTED!not-for-mail NNTP-Posting-Date: Fri, 02 Aug 2013 12:35:06 -0500 From: "Chris Uppal" Newsgroups: comp.lang.java.programmer References: <8fe57dc2-a323-4821-941c-4036663cbce5@googlegroups.com> <51f93cc4$0$291$14726298@news.sunsite.dk> <699768ec-b0b7-4752-a373-b58b8a39e32e@googlegroups.com> <16e55f41-fdc1-42d1-8819-f2d0ebcffb52@googlegroups.com> Subject: Re: What is so bad aboud Thread.stop() ? Date: Fri, 2 Aug 2013 18:35:08 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5512 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 Message-ID: Lines: 15 X-Usenet-Provider: http://www.giganews.com X-AuthenticatedUsername: NoAuthUser X-Trace: sv3-HRVEXQ09zq1/bU3lPJX8xONY9tpZFZrhUjQ3jSv74cdTYRHrcBCTJ/7PlBwE3W9l6ldJ08iRk8s6kK1!1t+lA3V2d1KDjFgrs0+9ntvcFll49FSQCmxJlFFYZJCFQ+FVVXSCPmu6CMitROOkRx9FxGhY9Q== X-Complaints-To: abuse@btinternet.com X-DMCA-Complaints-To: abuse@btinternet.com X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.40 X-Original-Bytes: 2050 Xref: csiph.com comp.lang.java.programmer:24879 taqmcg@gmail.com wrote: > I think Lew shares the apprehension I had had that it does something > magical and brings the thread down instantly, it seems clear that its > behavior is dangerous but bounded. Can the behaviour of Thread.stop() be relied on ? For an API that has been deprecated since the early Pleistocene, (and which -- if my very vague memory is roughly correct -- has never been implemented correctly anyway) it seems that implementers have the right to do practically anything. It's not as if we haven't been warned. -- chris