Re: Advice on abort

["REH" <spamjunk@stny.rr.com>]

Poul-Erik Andreasen wrote:
> REH wrote:
> > What are the best options when a task needs to be terminated, but
> > signaling the task may not be possible?  We have tasks that sometimes
> > need to be terminated, but may potentially be blocked on a resource,
> > such as a socket.  Currently we use OS-specific calls to terminate the
> > task, but I've never liked that.  I've been thinking of using the abort
> > statement, but I don't think that's very graceful either.  I also would
> > rather not complicate the code (or force polling behavior) by making
> > the sockets non-blocking.  Any advice?
> >
> One poosibillty is too use asyncronius transfer of control. Somthing
> like this.
>
>
> select
>     call.foo_entry  -- this i is a guarded entry in a protected
> object or 				--	another task
>     -- her can you have anything yuo may need to clean up after the abort
> then abort
>     listen_to_socket  this is the function wich may be blocked
> end select
>
> Thee foo_entry basicly dosen't need to do anything. an you have onother
> procedure or entry to open it.
>
>
> PEA.

I was once advised never to use ATC because it is very slow.  Is this
true?  It was in reference to GNAT.