Time to put a stop to Thread.stop? (original) (raw)

Chris Kirk kirkch at googlemail.com
Thu May 16 08:19:46 UTC 2013

Dropping some of the accrued baggage would be good. Java has gone an incredible distance without having a clear out. I for one believe that it deserves one.

The way that @Retired is being proposed to being used makes me think that I misunderstand the intent of @Deprecated. Doesn't @Deprecated mean, move off of this class/method. It has been superseded here are some notes on what has replaced it. We intend to remove it at some point in the future. If you ignore this warning then you risk having your program break in an upgrade of the library.

> Interesting suggestions but I for one do not think that after 15 years of > deprecation we need to go to such lengths to keep stop(Throwable) on > life-support - it is @Deceased in my opinion :) > Hi David, In fact, I fully agree for Thread.stop we should probably just do as you suggest and kill it :) but my interest shifted to the @Retired annotation which could be a nice general thing to have (Thread.stop could actually be a test case for it). Ideally, by Java 9, we could go through most of the @Deprecated and convert them to @Retired and give one platform lifetime to make people adjust their code. Java 10 could be finally free of all those ancient vestiges of a glorious past :) Cheers, Mario -- pgp key: http://subkeys.pgp.net/ PGP Key ID: 80F240CF Fingerprint: BA39 9666 94EC 8B73 27FA FC7C 4086 63E3 80F2 40CF IcedRobot: www.icedrobot.org Proud GNU Classpath developer: http://www.classpath.org/ Read About us at: http://planet.classpath.org OpenJDK: http://openjdk.java.net/projects/caciocavallo/ Please, support open standards: http://endsoftpatents.org/

More information about the core-libs-dev mailing list