Time to put a stop to Thread.stop? (original) (raw)
Martin Desruisseaux martin.desruisseaux at geomatys.fr
Wed May 15 08:39:22 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 ]
Le 15/05/13 10:05, David Holmes a écrit :
There is a huge difference between blowing away a complete process with kill and having a single thread starting to propagate an async exception, unwinding its stack and executing finally blocks with completely broken state invariants.
Given the risk, what about a mechanism similar to the one which currently hides the Sun internal packages from the compilation phase but not yet from the runtime phase? Would it be acceptable to have 'javac' and 'javadoc' woking as if the 'Thread.stop(Throwable)' method did not existed anymore, while having the method still working (for now) at runtime for existing libraries? Maybe with an annotation yet stronger than @Deprecated.
Martin- 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 ]