Exceptions; Re: Some remarks by Cezary Zielinski...

All, for reference,

> > From experience I know that the code devoted to
> > failure mode is usually as large as the one dealing with normal functioning.
> > There are 3 kinds of failure communication due to:
> > 1. Non fatal errors (e.g. user demanding something that is beyond the
> > capabilities of the system)
> > 2. Fatal errors (e.g. robot hardware malfunction - for instance somebody
> > forgot to power up the motors)
> > 3. System errors (e.g the control network malfunctioned)
> > Reactions to all of those errors need to be included in the specification of
> > the modules.
> 
> I agree with this suggestion. Maybe you have some concrete examples
> that you can post on the mailinglist?

To my knowledge, the first who successfully 'compiled' this experience (etc.)
into a paper was:

@Article{robexcept,
  author =       "I.J. Cox and N.H. Gehani",
  title =        "Exception Handling in Robotics",
  journal =      "IEEE Computer",
  year =         1989,
  month =        "March"
}

-- Klas
-----------------------------------------------------------------------
   o--<    mail: Klas Nilsson, Department of Computer Science
    \      Lund Institute of Technology, Box 118, S-221 00 LUND, Sweden
     O     phone: +46-(0)46-2224304 (work), +46-(0)46-370160 (home)
+->>[_]    mailto:[email protected]   http://www.cs.lth.se/~klas
|
+-------<< Real-time << components << control << users << languages.