|Dartmouth BASIC, Tymshare SUPER BASIC|
BASIC-PLUS is an extended dialect of the BASIC programming language that was developed by Digital Equipment Corporation (DEC) for use on its RSTS/E time-sharing operating system for the PDP-11 series of 16-bit minicomputers in the early 1970s through the 1980s.
BASIC-PLUS was based on BASIC-8 for the TSS/8, itself based very closely on the original Dartmouth BASIC. BASIC-PLUS added a number of new structures, as well as features from JOSS concerning conditional statements and formatting. In turn, BASIC-PLUS was the version on which the original Microsoft BASIC was patterned.
Notable among the additions made to BASIC-PLUS was the introduction of string functions like MID$ and LEFT$, in addition to Dartmouth's original all-purpose CHANGE command. In future versions of the language, notably Microsoft's, CHANGE was removed and BASIC-PLUS's string functions became the only ways to perform these sorts of operations. Most BASICs to this day follow this convention.
The language was later rewritten as a true compiler as BASIC-Plus-2, and was ported to the VAX-11 platform as that machine's native BASIC implementation. This version survived several platform changes, and is today known as VSI BASIC for OpenVMS.
Users would sit at a terminal and type in programming language statements. The statements could either be entered into the system's command interpreter directly, or entered into a text editor, saved to a file, and loaded into the command interpreter from the file. Errors in source code were reported to the user immediately after the line was typed.
As a smart terminal with cursor control could not be guaranteed, BASIC-PLUS used the common system of prefixing all source code with a line number. The code was edited by typing in the number and then changing the contents of the following code. A line of code could be removed by typing in its line number and nothing else, thereby setting it to an empty line.
The virtual address space of an RSTS/E user was limited to a little less than 64KB of space. Using BASIC-PLUS, about half of this virtual address space was used by the combined command interpreter and run-time library (named the Run Time System on RSTS/E). This limited user programs to about 32 kB of memory.
Large programs were broken up into various pieces by use of the
CHAIN statement, and programs could chain to specific line numbers in a secondary program to indicate that a program should begin execution at a different point from its first line. This feature of chaining to a certain line number allowed programs to signal to each other that they were being called from another program. The use of a shared memory section called core common also allowed programs to pass data to each other as needed. Disk files could also be used but were slower.
To conserve memory, the system included a garbage collecting memory manager, used for both string data and byte-code.
A running program could be interrupted, have variables examined and modified, and then be resumed.
BASIC-PLUS is patterned closely on later versions of Dartmouth BASIC, including its powerful
MAT commands. On top of this, DEC added a number of unique flow-control structures.
Line numbers were positive integers from 1 to 32767. Logical lines of code could be continued on multiple physical lines by using a line feed at the end of a line instead of the normal carriage return character. For ease of external editing of the source file, later versions of BASIC-PLUS also allowed the
& character as a line continuation character.
Multiple statements could be placed on a single line using
: as the statement separator. The system allowed tabs to be used as inline whitespace, and was used to make loops more clear, as in modern languages. Comments used either the
REM keyword or the
! character, as opposed to MS BASICs, which used
PRINT 1,2,3 would output 1, 2 and 3 in a spaced-out fashion, while
PRINT 1;2;3 would leave a single space and produce "1 2 3".[a]
INPUT allowed a prompt string to be specified, but used the semicolon to separate it rather than the comma;
INPUT "WHAT IS THE VALUE";A.
Strings could be delimited by single or double quotes. In addition to the
ASCII functions that converted single characters to and from string format, BASIC-PLUS also supported Dartmouth's powerful
CHANGE iterated the string and returned each character's ASCII value as a slot in a numeric array. For instance,
CHANGE 'HELLO' TO X would return an array five elements long. One could reverse the operation as well,
CHANGE X TO A$ would read the individual numbers in the X array and convert it to a string.
BASIC-PLUS added the concept of "statement modifiers", JOSS-like conditions that could be applied to any statement. For instance,
PRINT I IF I <> 10 is the equivalent of
IF I <> 10 THEN PRINT I The opposite was also provided,
PRINT I UNLESS I = 10 was the equivalent of
IF I <> 10 THEN PRINT I.
FOR loops worked as in other versions of BASIC, and the
NEXT command could not be used in an expression to exit early. Instead, the
WHILE keywords could be used to control early exits. For instance,
FOR I=1 UNTIL I=10 continue looping until I=10, with the assumption that following code would set the value of I, meaning it might not exit after 10 iterations but as soon as the code set I to 10. Modifiers could also be used to build compact one-line loops, for instance,
X=X+1 WHILE X<100 would loop until X was 100.
Variable names in the early versions of BASIC-PLUS could be a single letter or a single letter followed by a single digit. With the inclusion of "Extend mode" in later versions, variable names could be up to 29 characters long, and dot (.) was added as a permitted character. Every variable name still had to begin with a letter.[b] As in most versions of BASIC, the
LET keyword, for variable assignment, was optional. It could set multiple variables to a single value, like
The language supported three data types; floating-point numbers, integers, and strings. Variables with no suffix were floating point (8 bytes, range 0.29×10−38 to 1.7×1038, up to 16 digits of precision). Integer variables (16-bit, range −32768 to +32767) were indicated with a
% suffix, string variables (variable length) were indicated with a
The list of mathematical and logical operators was typical of most BASICs, with some extensions. For math,
^ were supported, along with
** as an alternate form of
^ for computer terminals that might not have that character. Standard logical comparisons were
<>. One interesting addition was the
== operator, for "aproximately equal". This would return true if the two numbers would be printed the same, that is, their six most significant digits were the same. Logical operators included the typical
A AND B and
A OR B, along with
A XOR B,
A EQV B which return true if both A and B are true or both are false, and
A IMP B which is false if A is true and B is false and otherwise always true.
DIM statement could allocate one-dimensional and two-dimensional arrays of any of the three data types. The range of subscripts always began with 0 (but
MAT statements did not set elements in row 0 or column 0).
The language also included a number of
MAT commands to work with the entire array (or MATrix). The
MAT READ command would fill the matrix with values in a
MAT INPUT would fill the array with user-typed values, and
MAT PRINT would print out the elements in a 1D or 2D format.
MAT could also be used to set default values in a matrix using associated keywords, for instance,
MAT A=ZER would fill the A array with zeros.
TRN would transpose an entire matrix, and
INV would invert it. Additionally,
* could be used on matrixes, performing the associated matrix operation.
DIM# "virtual DIM" statement could map "virtual data array(s)" or "virtual array(s)" to a disk file, which allowed arrays larger than the computer's available memory (or even its address space), and allowed use of array elements to read, write, and extend disk files (persistent storage). They called this arrangement "virtual data storage" and "virtual core", but it did not use the modern approach of allocating the arrays and a memory-mapped file. Instead, a single buffer was used to store 512 bytes of data at a time, and when an entry in the virtual array was accessed, the corresponding data was read, and old data written, as required. The
CLOSE statement caused the buffer to be written back (if necessary) before closing the file. Because no additional sectors were cached, accessing data in the "wrong" order could multiply the number of disk accesses. Additional rules were imposed on virtual arrays, such that one datum could never span a record boundary: Each data type was aligned to a multiple of its size. Virtual strings were stored as fixed-length ASCIIZ data, with sizes restricted to 2, 4, 8, 16, 32, 64, 128, 256, or 512 bytes, and were accessed using
BASIC-PLUS was not an interpreter but a compile and go system: each line of BASIC was translated into "PPCODE" (Push-Pop Code) as it was entered, for subsequent fast execution on its virtual machine. These translations did not tokenize the BASIC lines but rewrote them for use on a stack machine; you could not translate these representations back to BASIC statements. This avoided the need to repeatedly decode the keywords as strings: once converted to PPCODE the keywords were numbers that pointed to routines to run that function. BASIC-PLUS included a
COMPILE command, but this was not a true compiler; this simply saved the program's PPCODE representation so that it did not have to be recompiled when the BASIC program was next loaded into memory. The system store a user's program in two formats. One was the editable source code in text format, created using the
SAVE command and normally placed in a .BAS file. The other was the PPCODE version of the program created by the
COMPILE command and saved to a .BAC file; .BAC files were smaller and loaded and ran faster, but could not be edited.
Main article: VSI BASIC for OpenVMS
A related product called Basic Plus 2 ("BP2" or BASIC-Plus-2), was later developed by DEC to add additional features and increased performance.
It used true compilation into threaded code and wrote its output to object files compatible with the machine code object files produced by the assembler and other language systems. These object files could be kept in libraries. A linker (the TKB taskbuilder) then created executable files from object files and the libraries. TKB also supported overlays; this allowed individual routines to be swapped into the virtual address space as needed, overlaying routines not currently being used. Additionally,
BP2 programs ran under the RSX Run Time System; this RTS only occupied 8KB of the user's virtual address space, leaving 56KB for the user's program. (RSTS/E version 9 introduced separate Instruction and Data space, and the "disappearing" RSX Run Time System, permitting up to 64KB of each of instruction code and data.) These two factors allowed individual BP2 programs to be much larger than BASIC-PLUS programs, often reducing the need for CHAINing among multiple programs.
Unlike BASIC-PLUS (which was only available on RSTS/E), BP2 was also available for the RSX-11 operating system. BP2 programs were also more compatible with the later VAX BASIC.
Microsoft BASIC was patterned very closely on BASIC-PLUS. Earlier versions of MS BASIC, the 1.x series, lacked integer variables, but these were added in the 2.x series that was found on many machines, including the later models of the Commodore PET and Commodore 64. The ability to place logical and loop commands in-line, like
I = I + 1 UNTIL I = 10 was not copied over and does not appear on any common version of microcomputer BASIC. MS BASIC also lacked the matrix commands.
FOR I=STOPwould be interpreted as
FOR I = S TO P.