Group: program proving
Group: user interface
Topic: aspect-oriented programming
Topic: error safe systems
Topic: object-defined exception handling
Topic: program proof via assertions
Topic: run-time assertions
| |
Summary
Exceptions may act as run-time type checking for argument validity or violation of the procedure's specifications. Some workers believe all exceptions should be of this sort, thereby removing the problem of exceptions resulting in side effects, and simplifying program proofs. (cbb 5/80)
Quotations
QuoteRef: hamiM3_1976 ;;27 axiom 5. a module controls rejection (errors) only of its own input
| QuoteRef: parnDL5_1972 ;;331 in effect section of module specification give error trap conditions then give order independent specification of state change
| Quote: a system should be intelligent, i.e., help the user and reduce workload; e.g., check all inputs for validity [»potaWA_1979]
| Quote: the "abstract" machine detects attempts to violate its specifications; such undesired events invoke traps [»parnDL10_1976b]
|
Related Topics
Group: program proving (10 topics, 311 quotes)
Group: user interface (75 topics, 1639 quotes)
Topic: aspect-oriented programming (2 items)
Topic: error safe systems (76 items)
Topic: object-defined exception handling (10 items)
Topic: program proof via assertions (61 items)
Topic: run-time assertions (25 items)
|