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.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no
	version=3.4.4
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!hp4nl!uva!mel!hm
From: hm@uva.UUCP (HansM)
Newsgroups: comp.lang.ada
Subject: Two questions
Message-ID: <674@uva.UUCP>
Date: 29 Mar 89 09:16:26 GMT
Sender: news@uva.UUCP
Reply-To: hm@uva.UUCP (Hans Mulder & Sjouke Mauw)
Organization: Faculteit Wiskunde & Informatica, Universiteit van Amsterdam
List-Id: <comp.lang.ada>

We are trying to understand Ada tasking and there are two things we fail to
understand:

1. When an exception is raised and not handled in a task body, the task
   is terminated and the exception is not further propagated, without
   notice (11.4.1.8).  Why is this?
   Is there a way to invoke the kind of traceback that occurs when an
   exception is propagated out of the main program?

2. When a task has completed its execution, termination is delayed until all
   dependent tasks have terminated (9.4.6).  As a result, our program
   fills up all memory with completed tasks unable to terminate.  Why is
   this?  Can something be done about it (without altering task dependency)?


We have the impression that Ada was designed to deal with a small
number of large tasks, whereas we are trying to create a large number
of small tasks.  Is this true?  Does it matter?

Can anybody enlighten us?

AdvTHANKSance

Hans Mulder		Sjouke Mauw
hm@uva.uucp		sjouke@uva.uucp
mcvax!uva!hm		mcvax!uva!sjouke