Time to put a stop to Thread.stop?

[Alan Bateman]

On 15/05/2013 08:00, Dawid Weiss wrote:
> :
>
> A much more needed addition to the standard library in place of
> Thread.stop() would be methods to acquire:
>
> 1) your own PID (this one is in planning for 1.8 or even has been
> added already),
> 2) forked process PID (?),
> 3) a way to kill the forked process (and possibly its sub-tree).
>
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. There has been a number of attempts at adding support for 
exposing the process-id. Implementation is trivial, the hard part has 
always been consideration for environments where they may not be a 1-1 
mapping. In any case, thanks for the comments and experiences on using 
Thread.stop.

-Alan.