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.6 required=5.0 tests=BAYES_05,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ima!inmet!ada-uts!stt
From: stt@ada-uts
Newsgroups: net.lang.ada
Subject: Re: Propagation of exceptions raised wi
Message-ID: <4700040@ada-uts>
Date: Fri, 20-Jun-86 11:05:00 EDT
Article-I.D.: ada-uts.4700040
Posted: Fri Jun 20 11:05:00 1986
Date-Received: Sun, 22-Jun-86 07:20:25 EDT
References: <325@cernvax.UUCP>
Nf-ID: #R:cernvax.UUCP:325:ada-uts:4700040:000:669
Nf-From: ada-uts!stt    Jun 20 11:05:00 1986
List-Id: <comp.lang.ada>


Quoting from the Ada RM, 11.4.1:4,8 ...
"If an exception is raised in the sequence of statements of a frame
that does not have a handler for the exception [ e.g.
your "raise TASK_CRASHED" ], execution of this sequence
of statements is abandoned.  The next action depends on
the nature of the frame:

. . .
  (d)  For a task body, the task becomes completed."

In other words, exceptions are not propagated out of task bodies.
Even the "master" is unaware that a task completed due to
an unhandled exception.  It only knows that the task completed somehow.

Just to confuse things, exceptions ARE propagated out
of accept bodies, to both the caller and the called task.