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=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Thread: 103376,c3c4ae45442f569e
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news1.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "Alex R. Mosteo" <devnull@mailinator.com>
Newsgroups: comp.lang.ada
Subject: Re: tasks and protected types
Date: Fri, 29 Apr 2005 14:55:38 +0200
Message-ID: <42722ECA.5060903@mailinator.com>
References: <1114747457.868019.93210@f14g2000cwb.googlegroups.com>
 <m23bt9dik6.fsf@hugin.crs4.it>
 <1114771627.401153.78280@z14g2000cwz.googlegroups.com>
 <m2sm19bywq.fsf@hugin.crs4.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net Si12WHDqGDilWfWPGnBtuwANJbZALKebUlIDBbe+xFmP5APjw=
User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317)
X-Accept-Language: en-us, en
In-Reply-To: <m2sm19bywq.fsf@hugin.crs4.it>
Xref: g2news1.google.com comp.lang.ada:10818
Date: 2005-04-29T14:55:38+02:00
List-Id: <comp.lang.ada>

Jacob Sparre Andersen wrote:

> If you will accept a guess: An exception is raised in the first accept
> call.  This means that the D1 task terminates (they do that, when you
> have exceptions), 

For the newbie information, they terminate if the exception is not 
managed somewhere in the task. For this reason having a top level 
exception manager in each task for reporting is a good idea.

task X is
begin
    ---
exception
    when E : others =>
       --  <your logging stuff here>
end;

> If you will accept a guess: An exception is raised in the first accept
> call.  This means that the D1 task terminates (they do that, when you
> have exceptions), but without finishing the accept block.  This leaves
> Manage hanging, waiting for D1 (which is dead) to finish its accept
> block.

I'm too guessing, but I think that when an exception happens inside an 
accept, the task gets the exception and the caller gets a Tasking_Error 
exception. Kinda like if the exception "splits" and goes to the two 
threads. Can someone confirm?