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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,790d824907970cc3
X-Google-Attributes: gid103376,public
From: Matthew Heaney <matthew_heaney@acm.org>
Subject: Re: Exception Propagation
Date: 1999/06/09
Message-ID: <m3wvxef8zw.fsf@mheaney.ni.net>#1/1
X-Deja-AN: 487309848
References: <b3T63.5112$y6.2934699@WReNphoon3> <7jh857$ej$1@nnrp1.deja.com>
 <375CC549.7EDFB885@spam.com> <7jk1c1$t8$1@nnrp1.deja.com>
NNTP-Posting-Date: Tue, 08 Jun 1999 18:33:02 PDT
Newsgroups: comp.lang.ada
Date: 1999-06-09T00:00:00+00:00
List-Id: <comp.lang.ada>

Robert Dewar <robert_dewar@my-deja.com> writes:

> I would have preferred that an unhandled exception in a task
> caused termination of the entire program, you can always get
> the bizarre effect in the RM if you really want it by doing:
> 
>       exception when others => null;
> 
> at the outer level of a task


I don't understand this comment.  

Given this task body:

  task body T is
    ...
  begin
    ...
  exception
    when others => null;

  end T;


Are you saying that if an exception occurs, that that exception handler
will cause behavior other than silent termination of task T?