NBS Minimal BASIC Test Programs: Version 2, User's Manual, Volume 13 |
From inside the book
Results 1-5 of 100
Page 6
Those who wish to know how to interpret the results of program execution should also read section 3 and then section 4 for the general rules interpretation and section 5 for information peculiar individual programs and groups of ...
Those who wish to know how to interpret the results of program execution should also read section 3 and then section 4 for the general rules interpretation and section 5 for information peculiar individual programs and groups of ...
Page 8
For control , there is a GOTO , an IF which can cause control to jump to any line in the program , a GOSUB and RETURN for internal subroutines , a FOR and NEXT statement to execute loops while incrementing a control - variable , and a ...
For control , there is a GOTO , an IF which can cause control to jump to any line in the program , a GOSUB and RETURN for internal subroutines , a FOR and NEXT statement to execute loops while incrementing a control - variable , and a ...
Page 12
A given program , for instance , might execute without exceptions on one standard implementation , and cause overflow on another , with a notably different numeric result . The programs that test features in these areas call for ...
A given program , for instance , might execute without exceptions on one standard implementation , and cause overflow on another , with a notably different numeric result . The programs that test features in these areas call for ...
Page 13
It may be thought of as an algorithm which the user ( not the programs ) must execute in order to interpret correctly the effect of submitting a test program to implementation . an The procedure for error handling in Figure 1 speaks of ...
It may be thought of as an algorithm which the user ( not the programs ) must execute in order to interpret correctly the effect of submitting a test program to implementation . an The procedure for error handling in Figure 1 speaks of ...
Page 16
We have tried to keep the storage required for execution within reasonable bounds . Array sizes are as small as possible , consistent with adequate testing . No program exceeds 300 lines in length . The programs print many informative ...
We have tried to keep the storage required for execution within reasonable bounds . Array sizes are as small as possible , consistent with adequate testing . No program exceeds 300 lines in length . The programs print many informative ...
What people are saying - Write a review
We haven't found any reviews in the usual places.
Other editions - View all
Common terms and phrases
20 PRINT 40 PRINT SECTION ACCEPT THE PROGRAM ACCOMPANIED BY DOCUMENTATION ACCURACY ACTUAL ALLOWING ANSI STANDARD ARGUMENT ARRAY ASSIGNED BASIC TEST PROGRAMS CHARACTERS COLUMN COMPUTED CONSTANTS CONTAINING CONTROL DATA DIGITS DISPLAYED END END TEST ENTER ERROR EVALUATION EXACT EXECUTION EXPECTED FOLLOWING FUNCTION GOSUB GOTO IDENTIFYING THE EXCEPTION implementation INFORMATIVE TEST INPUT INPUT-REPLY ITEM LINE LOOP MEASURE MESSAGE IDENTIFYING MINIMAL BASIC TEST NBS MINIMAL BASIC NEGATIVE NON-STANDARD FEATURE NOTE NUMERIC EXPRESSIONS OCCUR OK OK OK operations ORDER OUTPUT OVERFLOW PASS THIS TEST POSITIVE PRINT 40 PRINT PRINT BEGIN TEST PRINT END PROGRAM PRINT END TEST PRINT PROGRAM FILE PRINT THIS SECTION PRINT TO PASS PROCESSOR PROGRAM NUMBER PROGRAM TESTS PROGRAMS USER'S MANUAL READ REFERENCE REFS REJECT THE PROGRAM REPORTED RESULT RETURN RND FUNCTION SECTION TESTS SPACE STATEMENT STEP STRING SUBSCRIPT SUPPLIED TERMINATE TEST FAILED TEST OK TEST PASSED TYPE UNDERFLOW VALUE VARIABLE ZERO