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 13
Page 1
... determine whether or not a given feature is correctly implemented , others produce output which the user must then interpret to some degree . This manual describes how the programs used SO as to interpret correctly the tests . Such ...
... determine whether or not a given feature is correctly implemented , others produce output which the user must then interpret to some degree . This manual describes how the programs used SO as to interpret correctly the tests . Such ...
Page 2
... Determining Implementation Conformance 10 11 3.1 Test programs as test data , not algorithms .. 11 3.2 Special Issues Raised by the Standard Requirements .... 12 3.2.1 Implementation - defined features 12 4.3 4 3.2.2 Error and Exception ...
... Determining Implementation Conformance 10 11 3.1 Test programs as test data , not algorithms .. 11 3.2 Special Issues Raised by the Standard Requirements .... 12 3.2.1 Implementation - defined features 12 4.3 4 3.2.2 Error and Exception ...
Page 9
... determine whether or not it obeys all the rules laid down in the standard . These rules are mostly spelled out in the syntax sections of the standard using a variant of Backus - Naur Form ( BNF ) . They are supplemented , however , by ...
... determine whether or not it obeys all the rules laid down in the standard . These rules are mostly spelled out in the syntax sections of the standard using a variant of Backus - Naur Form ( BNF ) . They are supplemented , however , by ...
Page 10
... determined . The difference in the way conformance is defined for programs and processors radically affects the test methodology by which we determine whether the standard is met . The relevant point is that there currently is no way to ...
... determined . The difference in the way conformance is defined for programs and processors radically affects the test methodology by which we determine whether the standard is met . The relevant point is that there currently is no way to ...
Page 11
Version 2, User's Manual John V. Cugini. 3 DETERMINING IMPLEMENTATION CONFORMANCE 3.1 or no . Test Programs As Test Data , Not Algorithms The test programs do not embody some definitive algorithm by which the question of processor ...
Version 2, User's Manual John V. Cugini. 3 DETERMINING IMPLEMENTATION CONFORMANCE 3.1 or no . Test Programs As Test Data , Not Algorithms The test programs do not embody some definitive algorithm by which the question of processor ...
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