Re: terminate applications

[Marin David Condic <nobody@noplace.com>]

I'd consider it a bug too. However, I think the compiler writers 
responsible for it consider it a "feature" or at least a "bug" that 
belongs to Windows. It was too difficult to track down the ultimate 
cause for a program that just wasn't that important and could take a 
control-C kill at the point where the abortion of the environment task 
would not work. It just seemed to me that passing the buck around wasn't 
very productive. If one can't make the abortion of the environment task 
work as expected, then come up with an alternative that absolutely, 
positively, double-your-mony-back-if-not-completely-satisfied, *will* 
work. Other programming languages provide some means of program 
termination (Pascal had a "HALT" instruction IIRC...) so its not as if I 
was dreaming up some wild-eyed fanatical scheme from the lunatic fringe. :-)

MDC



Randy Brukardt wrote:
> 
> Of course, there is no recourse to a kill -9 or pulling the plug. But those
> should be a really last resort. (Of course, I've never seen a program with a
> correct runtime hang when it was aborted. I had some programs do that when
> the runtime was screwed up, but no other time. If checks are not suppressed,
> I'd consider it a bug.)
> 

-- 
======================================================================
Marin David Condic
I work for: http://www.belcan.com/
My project is: http://www.jast.mil/

Send Replies To: m c o n d i c @ a c m . o r g

     "In general the art of government consists in taking as
     much money as possible from one class of citizens to give
     to the other."

         --  Voltaire
======================================================================