Time to put a stop to Thread.stop? (original) (raw)
Dawid Weiss dawid.weiss at gmail.com
Wed May 15 08:48:29 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 ]
We have JEP 102 to update Process. Some of the low hanging fruit, like Process.destroyForcibly, went into jdk8 so they have been removed from the JEP.
Thanks for the pointer, Alan. I fully agree with the rationale:
"Long-standing shortcoming in the platform [...] Long requested by developers."
[...] the hard part has always been consideration for environments where they may not be a 1-1 mapping.
I think this should be handled by allowing those methods to throw UnsupportedOperationException or some other form of signalling the operation as unsupported. 99% of the operating systems in existence will have (trivial?) support for these operations -- they are the very core of what an operating system is (process management), right?.
Dawid
- 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 ]