🚀 go-pugleaf

Phil Helms (PHIL@MASH.Colorado.EDU) writes:
>As a solution, you could have two types of message on an abend:
>
>    1.  A less detailed informational message, in the language of the user's
>        choice.
>    2.  A more detailed technical message, probably cryptic to the
>        uninitiated, but understandable to support staff, whether that
>        support staff is the user, a fellow employee of the user, or someone
>        on the other side of the globe.
>
>The first type of message could appear as a detailed addendum to the second
>type.
>
>In this way, necessary information about an abend is readily available to
>both user and support staff, in the language or languages that they require.

My own suggestion is to "split the difference:"  give a
    fairly terse but understandable message in the program,
    but provide a reference manual containing more detail.
    This way the user can get *some* idea of what happened,
    but if the explanation is not enough, there is the
    option of the more detailed description.


               * * * * * * * * * * * * * * * * *
Mike Titus, Programmer                  /\   Summer Institute
SIL                                    /  \        of
7500 West Camp Wisdom Road            /SIL \   Linguistics
Dallas, Texas  75236-5699            --------
U.S.A.
Voice    : (214) 709-2400		* Internet <titus@dallas.sil.org>
Facsimile: (214) 709-3387		* HAM radio (not on packet) KB4ABZ