Re: exception handling

Herman Bruyninckx wrote :
| I am wondering whether one should try to catalogue errors in a
| classification of ``importance''... In my view, each component in the
| system should have a means (i) to detect whatever errors it can
| detect, (ii) to react to them as far as it can react to them, and
| (iii) report about them to the ``outside'' world. The architecture of
| how one constructs a system out of components then defines implicitly
| what is the importance of an error.
| 
| This view of mine has not matured very much, so don't take it without
| a big grain of salt :-)

I agree very much with your view.

I would only add that it can be useful to have at least one particular
'fatal report' for codels. It can be used to indicate a catastrophic
failure and inform the component that has executed this codel that it is
now in a dangerous state (something equivalent to the 'abort()' function
call).

[in GenoM this is the 'ZOMBIE' state of the execution engine]