What is a checking component? When should it be used?
A23: Many components have operations with preconditions. That means that before calling such an operation, the programmer must make sure that its preconditions are satisfied. If they are not, the operation is allowed to do anything it pleases, including crashing the program in most unpleasant ways. While it may seem like a good idea to force every operation to check its preconditions, doing so would result in very severe and unnecessary efficiency penalties. The reason it is not always necessary to check the preconditions is that in the debugged or verified program one can be certain that they are satisfied. However, during the testing and debugging of a program, it is very helpful to know that if the program is calling an operation when its preconditions are not satisfied, a helpful message to that extent will be output and the program will stop immediately. To facilitate this, a special “checking” implementation of every component should be constructed. This implementation serves as
Related Questions
- We currently use ADAESI, which uses 20-byte non-delimited SSF rules for security checking. Can these same rules be used by SECURITRE, so that we can avoid having to re-enter them?
- What information does the School District - Component Tax Data table present, and how can it be used?
- How Do I Know If the Used Cars Engine Is Bad by Checking Oil?
