NBS Minimal BASIC Test Programs: Version 2, User's Manual, Issue 500, Part 1 - Issue 570, Part 1U.S. Department of Commerce, National Bureau of Standards, 1980 |
From inside the book
Results 1-5 of 12
Page 11
... rejects a standard program , it certainly fails to conform to the standard ; yet this is a type of behavior which can hardly be detected by the program itself : only a human observer who knows that the processor must accept standard ...
... rejects a standard program , it certainly fails to conform to the standard ; yet this is a type of behavior which can hardly be detected by the program itself : only a human observer who knows that the processor must accept standard ...
Page 12
... reject the program with a message to the user noting the reason for rejection , or , if it accepts the program , it must be accompanied by documentation which describes the interpretation of the construction . If a condition defined as ...
... reject the program with a message to the user noting the reason for rejection , or , if it accepts the program , it must be accompanied by documentation which describes the interpretation of the construction . If a condition defined as ...
Page 13
... rejecting a program . The glossary ( sec . 19 ) of the standard defines accept as " to acknowledge as being valid " . A processor , then , is said to reject a program if it in some way signifies to the user that an invalid construction ...
... rejecting a program . The glossary ( sec . 19 ) of the standard defines accept as " to acknowledge as being valid " . A processor , then , is said to reject a program if it in some way signifies to the user that an invalid construction ...
Page 14
... rejected ) if appropriate error message processor PASSES else processor FAILS ( did not report reason for rejection ) endif endif endif * note that all implementation - defined features must be documented ( See Appendix C in the ANSI ...
... rejected ) if appropriate error message processor PASSES else processor FAILS ( did not report reason for rejection ) endif endif endif * note that all implementation - defined features must be documented ( See Appendix C in the ANSI ...
Page 19
... reject the to the user noting the reason for if it accepts the program , it must be accompanied which describes the interpretation of the program with rejection , a col or , by documentation message construction . Testing this ...
... reject the to the user noting the reason for if it accepts the program , it must be accompanied which describes the interpretation of the program with rejection , a col or , by documentation message construction . Testing this ...
Common terms and phrases
72 characters 8.4 PROGRAM NUMBER algorithm allowed ANSI ANSI standard argument assignment BASIC Test Programs behavior Computer Science context Control Statements correctly DEF statement division by zero documentation endif error measure error programs ERROR REFS error tests EVALUATION OF NUMERIC Exception Handling EXCEPTION REFS exception report exception tests execution FOR-BLOCKS FOR-STATEMENT functional group GOSUB and RETURN GOTO Implementation Conformance implementation-defined features Informative Tests INPUT exception input-reply internal interpretation keyword language standard LINE-NUMBERS machine infinity Minimal BASIC Test non-fatal exceptions NUMERIC CONSTANTS NUMERIC EXPRESSIONS ON-GOTO operations OPTION BASE pass/fail message passes or fails PBASIC PRINT processor FAILS PROGRAM NUMBER EXCEPTION program output programming language programs test pseudorandom QUOTED STRINGS CONTAINING recovery procedure reply requirements RND FUNCTION rules Science and Technology self-checking semantic significand simple software testing source code specified Standard Capabilities standard program syntax test fails TEST PASSED test system UNDERFLOW USER-DEFINED FUNCTION Version ZERO