Previous: Terminology and notation, Up: Terminology and notation [Contents][Index]
An application behavior is a behavior on which it is intended that the design of applications will be based. Most of the behaviors specified in this document are application behaviors. We sometimes say that “applications may expect” a certain behavior to emphasize that that behavior is an application behavior.
After an irrecoverable failure, the behavior of a Libmarpa application is undefined, so that there are no behaviors which can be relied on for normal application processing, and therefore, there are no application behaviors. In this circumstance, some of the application behaviors become diagnostic behaviors. A diagnostic behavior is a behavior which it is suggested that the programmer may attempt in the face of an irrecoverable failure, for testing, diagnostics and debugging. They are hoped for, rather than expected, and intended to allow the programmer to deal with irrecoverable failures as smoothly as possible. (See Failure.)
In this document, a behavior is a diagnostic behavior only if that is specifically indicated. Applications should not be designed to rely on diagnostics behaviors. We sometimes say that “diagnostics may attempt” a certain behavior to emphasize that that behavior is a diagnostic behavior.