NBS Minimal BASIC Test Programs: Version 2, User's Manual, Volume 13U.S. Department of Commerce, National Bureau of Standards, 1980 |
From inside the book
Results 1-5 of 18
Page 3
... Arrays .. Standard Capabilities . Exceptions . Errors ... 5.9 Control Statements . 33 34 34 34 34 35 5.9.1 GOSUB and RETURN .. 35 5.9.2 ON - GOTO .. 36 5.10 READ , DATA , and RESTORE . 36 5.10.1 Standard Capabilities .. 36 5.10.2 ...
... Arrays .. Standard Capabilities . Exceptions . Errors ... 5.9 Control Statements . 33 34 34 34 34 35 5.9.1 GOSUB and RETURN .. 35 5.9.2 ON - GOTO .. 36 5.10 READ , DATA , and RESTORE . 36 5.10.1 Standard Capabilities .. 36 5.10.2 ...
Page 7
... array manipulation . The current expectation is for ANSI adoption of this standard sometime in 1982. It is probable that such a standard for a full version of BASIC would be adopted as Federal Information Processing Standard . a 2.2 The ...
... array manipulation . The current expectation is for ANSI adoption of this standard sometime in 1982. It is probable that such a standard for a full version of BASIC would be adopted as Federal Information Processing Standard . a 2.2 The ...
Page 8
... array manipulation and has only rudimentary control structures . Although BASIC was originally designed for ... arrays are allowed , but only for numeric data , not string . For control , there is a GOTO , an IF which can cause control ...
... array manipulation and has only rudimentary control structures . Although BASIC was originally designed for ... arrays are allowed , but only for numeric data , not string . For control , there is a GOTO , an IF which can cause control ...
Page 12
... array . In the BASIC standard , the first case is called an error , and the second an exception , and in order to conform , a processor must take certain actions upon encountering either sort of anomaly . Given a program with a ...
... array . In the BASIC standard , the first case is called an error , and the second an exception , and in order to conform , a processor must take certain actions upon encountering either sort of anomaly . Given a program with a ...
Page 16
... Array sizes are as small as possible , consistent with adequate testing . No program exceeds 300 lines in length . The programs print many informative messages which may be changed without affecting the outcome of the tests . If your ...
... Array sizes are as small as possible , consistent with adequate testing . No program exceeds 300 lines in length . The programs print many informative messages which may be changed without affecting the outcome of the tests . If your ...
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