Re: Ada.Task_Identification.Abort_Task (Environment_Task) ;

["Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org>]

Yeah, in this particular instance, it really is just a matter of killing the
whole process and not worrying about finalization or the state of anything.
The OS should be able to clean up anything that matters and I just want the
program to stop. Obviously, this sort of thing could be very dangerous in
the wrong setting because you do avoid finalization and there might be cases
where things would be left in an unknown state. (Files not being properly
updated, for example.) But its not an uncommon need even in embedded
computers. Sometimes you might find yourself in some sort of corrupt state
and the easiest answer is to double-stroke the watchdog timer and force the
computer into a reset that re-initializes the whole thing. It would be nice
if Ada provided a standard way of accomplishing this.

MDC
--
Marin David Condic
Senior Software Engineer
Pace Micro Technology Americas    www.pacemicro.com
Enabling the digital revolution
e-Mail:    marin.condic@pacemicro.com


"Robert A Duff" <bobduff@shell01.TheWorld.com> wrote in message
news:wcc8z46pbcl.fsf@shell01.TheWorld.com...
>
> But note that with such a feature, whatever finalization actions you
> wrote will be skipped.  (If they aren't skipped, then the feature
> doesn't do what you said above, because finalization might loop.)
> If you're running on a real operating system, it might be perfectly OK
> to skip finalization, since the OS has to clean up anyway.
>