Re: Structured exception information

[Simon Wright <simon.j.wright@mac.com>]

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> raise Hardware_Error with 
>  "digital pot card did not respond to serial number request";
>
> raise Hardware_Error with
>   "digital pot card responded with wrong byte count to serial number" &
>   request (got" & Stream_Element_Offset'Image (Data_Last) & ")";
>
> raise Parameter_Error with
>   "motor" & Integer'Image (Module.Ramp_Motor_Index) & 
>   " Disable_Encoder_Model not set";
>
> raise Device_Error with
>   "can't open device " & C_Name (1 .. C_Name'Last - 1) & " : " &
>   Error_Type'Image (To_Error (GNAT.OS_Lib.Errno));

Our project (which has no HCI for the end users, just for the
maintenance engineer) might categorise these as

(a) and (b) possible hardware error, run BIT, get maintainer to
replace card if won't come good

(c) design error, reboot and report fault to support

(d) possible connection failure, run BIT, get maintainer to check
cabling

and in none of these is the original (English) text likely to help
front-line maintenance, though it will clearly help us to diagnose (c)
back at base.


It all depends who's going to be reading the error text.