Re: Exception Propagation

[Robert Dewar <robert_dewar@my-deja.com>]

In article <375CC549.7EDFB885@spam.com>,
  spamwithchipsplease@spam.com wrote:
> This feature has escaped me, or I have forgot  ( RM95 11.4(4)
> ), I've
> also checked RM83 and found it to be a feature of that
> language edition.
> I would rather the exception was propogated aleast this gives
> the option
> of deciding whether  the program  terminates or not.

Propagated to where? There really is no possibility of
propagation (you certainly do not want to introduce asynchronous
exceptions for this purpose!)

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


> Given the RM specification, I think a mandatory "when others"
> task level exception handler would be prudent.

Check your compiler, it may have an option for handling this
error situation nicely. But in general, yes, that's a good idea
(mandatory when others at the top level of a task).


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.