Time to put a stop to Thread.stop? (original) (raw)
Paul Sandoz paul.sandoz at oracle.com
Thu May 16 14:38:02 UTC 2013
- Previous message: Time to put a stop to Thread.stop?
- Next message: Time to put a stop to Thread.stop?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On May 16, 2013, at 2:00 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:
On 16/05/2013 11:03, David Holmes wrote:
Yes - I don't think we need @Retired as a stepping stone between @Deprecated and gone. But to date @Deprecated's notion of "some point in the future" is a future yet to materialize. :( But that more general debate deserves it's own thread. Yes, this proposal was always likely to start a more bigger discussion and that would be good to have. For this thread then the proposal is simply to scuttle Thread.stop(Throwable), maybe suspend/resume later. I'm not too concerned about jdk tests, we can change them. The only real concern is whether there are any real impact beyond the sleazy usages already mentioned.
How about doing a search for usages in all the jars on maven central?
IMHO it really helps drive the discussions deprecation if we have some empirical data.
Paul.
- Previous message: Time to put a stop to Thread.stop?
- Next message: Time to put a stop to Thread.stop?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]