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,f92fbb4a0420dd57 X-Google-Attributes: gid103376,public From: Mike Young Subject: Re: some questions re. Ada/GNAT from a C++/GCC user Date: 1996/04/01 Message-ID: <3160B2F1.260D@mcs.com>#1/1 X-Deja-AN: 145355934 references: <4jhe1v$m0g@dayuc.dayton.saic.com> <4jp17p$17vn@watnews1.watson.ibm.com> content-type: text/plain; charset=us-ascii organization: Fen Software, Inc. mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 2.0GoldB1 (Win95; I) Date: 1996-04-01T00:00:00+00:00 List-Id: Robert A Duff wrote: > > In article <4jp17p$17vn@watnews1.watson.ibm.com>, > Norman H. Cohen wrote: > >Jean Ichbiah correctly saw the chaos that could result from approach (b). > > I agree. > > >He chose approach (c) for an exception occuring while the child task was > >still elaborating the declarative part of its task body and (a) for an > >exception occuring once the child task entered the sequence of statements > >of its task body. > > IMHO, he should have chosen approach (c) for all exceptions. A master > awaits its dependent tasks before continuing. This would be the perfect > place to raise Tasking_Error if the dependent task(s) raise unhandled > exceptions. Instead, the dependents silently disappear, like Ms. Rigby, > and then the parent task continues merrily on its way. ======= This appears somewhat frightening to me, that I might catch exceptions from unknown and unspecified source at any given moment. What exactly should I do with this exception aside from terminating? (How is this different from SIGCHLD?) This might have the right intuitive feel if this behavior applied up until some known point where parent and child parts ways, but what point would that be? Mike.