🚀 go-pugleaf

>> [A long bit quoted from me]
> It is not quite as trivial as it sounds.  Some resources such as
> Windows are dependent upon other resources (ie. a Screen) being
> already allocated.  If you don't deallocate the resources in the
> correct order, things will blow up miserably.
 
But the correct order is almost invariably the opposite of that in which they were allocated.  Even when it is not, the order will often be unimportant.  What I described (or the equivalent of ARP's resource tracking, done automatically) would be enough to allow you to kill off most programs with very little mess.
 
Someone else pointed out that some programs mess around with various system structures, and that killing them would leave the computer very unhappy.  So what?  Set some flag somewhere to warn that killing this particular process right now is a bad idea.  It's impossible to handle every imaginable scenario perfectly, but that's no excuse to refuse to touch any of them.

--  
Jeff Petkau - via FidoNet node 1:140/22
UUCP: alberta!dvinci!weyr!Jeff.Petkau
Internet: Jeff.Petkau@weyr.FIDONET.ORG
Standard Disclaimers Apply...