From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Google-Thread: 103376,10d1a90a699d6cfc
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!postnews.google.com!q75g2000hsh.googlegroups.com!not-for-mail
From: Anh Vo <anhvofrcaus@gmail.com>
Newsgroups: comp.lang.ada
Subject: Re: Ada tasking question
Date: 19 Apr 2007 09:11:36 -0700
Organization: http://groups.google.com
Message-ID: <1176999096.607478.156900@q75g2000hsh.googlegroups.com>
References: <20070418201307.18a85fd9@cube.tz.axivion.com>
   <f05okq$bt8$1@jacob-sparre.dk>
   <462688E3.6050105@nowhere.com>
   <20070419005738.692eeeb6@cube.tz.axivion.com>
   <f06cqu$8f4$1@jacob-sparre.dk>
   <ygefy6wmsyx.fsf@hugsarin.dmusyd.edu>
NNTP-Posting-Host: 209.225.226.204
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1176999096 8141 127.0.0.1 (19 Apr 2007 16:11:36
 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 19 Apr 2007 16:11:36 +0000 (UTC)
In-Reply-To: <ygefy6wmsyx.fsf@hugsarin.dmusyd.edu>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0;
 .NET CLR 1.1.4322; InfoPath.1),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: q75g2000hsh.googlegroups.com; posting-host=209.225.226.204;
   posting-account=JVr7Xg0AAAAI3MbuARxMmvWLmA7qdJMx
Xref: g2news1.google.com comp.lang.ada:15122
Date: 2007-04-19T09:11:36-07:00
List-Id: <comp.lang.ada>

On Apr 19, 5:47 am, Jacob Sparre Andersen <spa...@nbi.dk> wrote:
> Randy Brukardt wrote:
> > I use something like:
>
> >      exception
> >           when Oops:others =>
> >                  Debug ("Worker Task Failed: exception raised: " &
> >                     Ada.Exceptions.Exception_Information (Oops));
> >     end Bucket_Worker;
>
> The exception handler allows us to notice when one of the tasks dies.
> But can we (re)start it somehow?  Or will we have to put an exception
> handler inside the processing loop, and that way keep the task
> running?

I always put exception handler inside the live_for_ever_task loop.
Only in a very rare case that it is very critical to terminate the
task. I will print out (log) lots of useful information before saying
Later Alligator.

AV