{"history":[],"article":{"id":"e0e8b401-4435-4467-9fb5-1a0771c51afd","title":"BASIC-PLUS","slug":"basic-plus","content":":::summary\n**Name:** BASIC-PLUS \n**Paradigm:** [imperative](https://bliptext.com/articles/imperative-programming) \n**Year:** 1970 \n**Influenced By:** [Dartmouth BASIC](https://bliptext.com/articles/dartmouth-basic), [Tymshare SUPER BASIC](https://bliptext.com/articles/tymshare-super-basic) \n**Influenced:** [Microsoft BASIC](https://bliptext.com/articles/microsoft-basic) \n**Operating System:** [RSTS/E](https://bliptext.com/articles/rsts-e) \n**Status:** Discontinued \n:::\n\n# \n**[BASIC](https://bliptext.com/articles/basic)-PLUS** is an extended dialect of the [BASIC](https://bliptext.com/articles/basic) [programming language](https://bliptext.com/articles/programming-language) that was developed by [Digital Equipment Corporation](https://bliptext.com/articles/digital-equipment-corporation) (DEC) for use on its [RSTS/E](https://bliptext.com/articles/rsts-e) time-sharing operating system for the [PDP-11](https://bliptext.com/articles/pdp-11) series of 16-bit [minicomputers](https://bliptext.com/articles/minicomputer) in the early 1970s through the 1980s.\nBASIC-PLUS was based on BASIC-8 for the [TSS/8](https://bliptext.com/articles/tss-8), itself based very closely on the original [Dartmouth BASIC](https://bliptext.com/articles/dartmouth-basic).\nBASIC-PLUS added a number of new structures, as well as features from [JOSS](https://bliptext.com/articles/joss) concerning conditional statements and formatting.\nIn turn, BASIC-PLUS was the version on which the original [Microsoft BASIC](https://bliptext.com/articles/microsoft-basic) was patterned.\nNotable 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.\nIn 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.\nMost BASICs to this day follow this convention.\nThe language was later rewritten as a true [compiler](https://bliptext.com/articles/compiler) as **BASIC-Plus-2**, and was ported to the [VAX-11](https://bliptext.com/articles/vax-11) platform as that machine's native BASIC implementation.\nThis version survived several platform changes, and is today known as [VSI BASIC for OpenVMS](https://bliptext.com/articles/vsi-basic-for-openvms).\n\n# Operation\nUsers would sit at a terminal and type in programming language statements.\nThe statements could either be entered into the system's [command interpreter](https://bliptext.com/articles/command-line-interface) directly, or entered into a [text editor](https://bliptext.com/articles/text-editor), saved to a file, and loaded into the [command interpreter](https://bliptext.com/articles/command-line-interface) from the file.\nErrors in source code were reported to the user immediately after the line was typed.\nAs 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.\nThe code was edited by typing in the number and then changing the contents of the following code.\nA line of code could be removed by typing in its line number and nothing else, thereby setting it to an empty line.\nThe virtual address space of an RSTS/E user was limited to a little less than 64KB of space.\nUsing 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](https://bliptext.com/articles/runtime-system) on RSTS/E).\nThis limited user programs to about 32 [kB](https://bliptext.com/articles/kilobyte) of memory.\nLarge programs were broken into separate executable pieces by use of the CHAIN statement, and programs could [chain](https://bliptext.com/articles/chain-loading) to specific line numbers in a secondary program to indicate that a program should begin execution at a different point from its first line.\nThis feature of chaining to a certain line number allowed programs to signal to each other that they were being called from another program.\nThe use of a shared memory section called [core common](https://bliptext.com/articles/core-common-area) also allowed programs to pass data to each other as needed.\n[Disk](https://bliptext.com/articles/hard-disk) files could also be used but were slower.\nTo conserve memory, the system included a garbage collecting memory manager, used for both string data and byte-code.\nA running program could be interrupted, have variables examined and modified, and then be resumed.\n\n# Syntax and features\nBASIC-PLUS is patterned closely on later versions of [Dartmouth BASIC](https://bliptext.com/articles/dartmouth-basic), including its powerful commands.\nOn top of this, DEC added a number of unique flow-control structures.\n\n## Editing\nLine numbers were positive integers from 1 to 32767.\nLogical lines of code could be continued on multiple physical lines by using a [line feed](https://bliptext.com/articles/line-feed) at the end of a line instead of the normal [carriage return](https://bliptext.com/articles/carriage-return) character.\nFor ease of external editing of the source file, later versions of BASIC-PLUS also allowed the & character as a line continuation character.\nMultiple statements could be placed on a single line using : as the statement separator.\nThe system allowed tabs to be used as inline whitespace, and was used to make loops more clear, as in modern languages.\nComments used either the REM keyword or the !\ncharacter, as opposed to MS BASICs, which used REM and '.\n\n## Standard statements\nThe PRINT command divided the screen into regions 14 spaces wide, and the comma was used to move between these locations; 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\".\nINPUT allowed a prompt string to be specified, but used the semicolon to separate it rather than the comma; INPUT \"WHAT IS THE VALUE\";A.\nStrings could be delimited by single or double quotes.\nIn addition to the CHR and ASCII functions that converted single characters to and from string format, BASIC-PLUS also supported Dartmouth's CHANGE command.\nCHANGE iterated the string and returned each character's ASCII value as a slot in a numeric array.\nFor instance, CHANGE 'HELLO' TO X would return an array with the five ASCII codes, 110, 105, 114, 114, 105, in elements 1 through 5, and the number 5, the length of the string, in element 0.\nOne 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.\n\n## Statement modifiers\nBASIC-PLUS added the concept of \"statement modifiers\", [JOSS](https://bliptext.com/articles/joss)-like conditions that could be applied to any statement.\nFor 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.\nFOR loops worked as in other versions of BASIC, and the NEXT command could not be used in an expression to exit early.\nInstead, the UNTIL and WHILE keywords could be used to control early exits.\nFor 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.\nModifiers could also be used to build compact one-line loops, for instance, X=X+1 WHILE X<100 would loop until X was 100.\n\n## Variables, expressions and matrixes\nVariable names in the early versions of BASIC-PLUS could be a single letter or a single letter followed by a single digit.\nWith 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.\nEvery variable name still had to begin with a letter.\nAs in most versions of BASIC, the LET keyword, for variable assignment, was optional.\nIt could set multiple variables to a single value, like LET A,B,C=10.\nThe language supported three data types; floating-point numbers, integers, and strings.\nVariables with no suffix were floating point (8 bytes, range 0.29 to 1.7, up to 16 digits of precision).\nInteger variables (16-bit, range −32768 to +32767) were indicated with a % suffix, string variables (variable length) were indicated with a $ suffix.\nThe list of mathematical and logical operators was typical of most BASICs, with some extensions.\nFor math, +, -, *, / and ^ were supported, along with ** as an alternate form of ^ for [computer terminals](https://bliptext.com/articles/computer-terminal) that might not have that character.\nStandard logical comparisons were =, <, >, <=, >=, and <>.\nOne interesting addition was the == operator, for \"approximately equal\".\nThis would return true if the two numbers would be printed the same, that is, their six most significant digits were the same.\nLogical operators included the typical NOT A, 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.\nThe DIM statement could allocate one-dimensional and two-dimensional arrays of any of the three data types.\nThe range of subscripts always began with 0 (but MAT statements did not set elements in row 0 or column 0).\nThe language also included a number of MAT commands to work with the entire array (or MATrix).\nThe MAT READ command would fill the matrix with values in a DATA statement, MAT INPUT would fill the array with user-typed values, and MAT PRINT would print out the elements in a 1D or 2D format.\nMAT 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.\nTRN would transpose an entire matrix, and INV would invert it.\nAdditionally, +, -, and * could be used on matrixes, performing the associated matrix operation.\n\n## File processing\nThe 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).\nThey 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](https://bliptext.com/articles/memory-mapped-file).\nInstead, 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.\nThe CLOSE statement caused the buffer to be written back (if necessary) before closing the file.\nBecause no additional sectors were cached, accessing data in the \"wrong\" order could multiply the number of disk accesses.\nAdditional 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.\nVirtual 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 LSET and RSET.\n\n# Virtual machine\nBASIC-PLUS was not an interpreter but a [compile and go system](https://bliptext.com/articles/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.\nThese 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.\nThis 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.\nBASIC-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.\nThe system stored a user's program in two formats.\nOne was the editable source code in text format, created using the SAVE command and normally placed in a .BAS file.\nThe 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.\n\n# BASIC Plus 2\nA related product called **Basic Plus 2** (\"BP2\" or **BASIC-Plus-2**), was later developed by DEC to add additional features and increased performance.\nIt used true compilation into [threaded code](https://bliptext.com/articles/threaded-code) and wrote its output to object files compatible with the machine code object files produced by the assembler and other language systems.\nThese object files could be kept in libraries.\nA linker (the TKB, also known as the taskbuilder) then created executable files from object files and the libraries.\nTKB also supported overlays; this allowed individual routines to be swapped into the virtual address space as needed, overlaying routines not currently being used.\nAdditionally, 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.\n(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.\nUnlike BASIC-PLUS (which was only available on RSTS/E), BP2 was also available for the [RSX-11](https://bliptext.com/articles/rsx-11) operating system.\nBP2 programs were also more compatible with the later [VAX BASIC](https://bliptext.com/articles/vsi-basic-for-openvms).\n\n# Comparison to MS BASIC\nMicrosoft BASIC was patterned very closely on BASIC-PLUS.\nEarlier 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](https://bliptext.com/articles/commodore-pet) and [Commodore 64](https://bliptext.com/articles/commodore-64).\nThe 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.\nMS BASIC also lacked the matrix commands.\n\n# Citations","current_revision":null,"created_by":"kACnuQmH5k9Nr5VNVEpVeg7XpvUmMctD","created_at":"2025-01-25T20:11:53.485Z","updated_at":"2025-01-25T20:11:53.485Z","search_vector":"'basic':2 'basic-plus':1 'plus':3","search_content":" \n**Name:** BASIC-PLUS \n**Paradigm:** [imperative](https://bliptext.com/articles/imperative-programming) \n**Year:** 1970 \n**Influenced By:** [Dartmouth BASIC](https://bliptext.com/articles/dartmouth-basic), [Tymshare SUPER BASIC](https://bliptext.com/articles/tymshare-super-basic) \n**Influenced:** [Microsoft BASIC](https://bliptext.com/articles/microsoft-basic) \n**Operating System:** [RSTS/E](https://bliptext.com/articles/rsts-e) \n**Status:** Discontinued \n \n\n# \n**[BASIC](https://bliptext.com/articles/basic)-PLUS** is an extended dialect of the [BASIC](https://bliptext.com/articles/basic) [programming language](https://bliptext.com/articles/programming-language) that was developed by [Digital Equipment Corporation](https://bliptext.com/articles/digital-equipment-corporation) (DEC) for use on its [RSTS/E](https://bliptext.com/articles/rsts-e) time-sharing operating system for the [PDP-11](https://bliptext.com/articles/pdp-11) series of 16-bit [minicomputers](https://bliptext.com/articles/minicomputer) in the early 1970s through the 1980s.\nBASIC-PLUS was based on BASIC-8 for the [TSS/8](https://bliptext.com/articles/tss-8), itself based very closely on the original [Dartmouth BASIC](https://bliptext.com/articles/dartmouth-basic).\nBASIC-PLUS added a number of new structures, as well as features from [JOSS](https://bliptext.com/articles/joss) concerning conditional statements and formatting.\nIn turn, BASIC-PLUS was the version on which the original [Microsoft BASIC](https://bliptext.com/articles/microsoft-basic) was patterned.\nNotable 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.\nIn 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.\nMost BASICs to this day follow this convention.\nThe language was later rewritten as a true [compiler](https://bliptext.com/articles/compiler) as **BASIC-Plus-2**, and was ported to the [VAX-11](https://bliptext.com/articles/vax-11) platform as that machine's native BASIC implementation.\nThis version survived several platform changes, and is today known as [VSI BASIC for OpenVMS](https://bliptext.com/articles/vsi-basic-for-openvms).\n\n# Operation\nUsers would sit at a terminal and type in programming language statements.\nThe statements could either be entered into the system's [command interpreter](https://bliptext.com/articles/command-line-interface) directly, or entered into a [text editor](https://bliptext.com/articles/text-editor), saved to a file, and loaded into the [command interpreter](https://bliptext.com/articles/command-line-interface) from the file.\nErrors in source code were reported to the user immediately after the line was typed.\nAs 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.\nThe code was edited by typing in the number and then changing the contents of the following code.\nA line of code could be removed by typing in its line number and nothing else, thereby setting it to an empty line.\nThe virtual address space of an RSTS/E user was limited to a little less than 64KB of space.\nUsing 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](https://bliptext.com/articles/runtime-system) on RSTS/E).\nThis limited user programs to about 32 [kB](https://bliptext.com/articles/kilobyte) of memory.\nLarge programs were broken into separate executable pieces by use of the CHAIN statement, and programs could [chain](https://bliptext.com/articles/chain-loading) to specific line numbers in a secondary program to indicate that a program should begin execution at a different point from its first line.\nThis feature of chaining to a certain line number allowed programs to signal to each other that they were being called from another program.\nThe use of a shared memory section called [core common](https://bliptext.com/articles/core-common-area) also allowed programs to pass data to each other as needed.\n[Disk](https://bliptext.com/articles/hard-disk) files could also be used but were slower.\nTo conserve memory, the system included a garbage collecting memory manager, used for both string data and byte-code.\nA running program could be interrupted, have variables examined and modified, and then be resumed.\n\n# Syntax and features\nBASIC-PLUS is patterned closely on later versions of [Dartmouth BASIC](https://bliptext.com/articles/dartmouth-basic), including its powerful commands.\nOn top of this, DEC added a number of unique flow-control structures.\n\n## Editing\nLine numbers were positive integers from 1 to 32767.\nLogical lines of code could be continued on multiple physical lines by using a [line feed](https://bliptext.com/articles/line-feed) at the end of a line instead of the normal [carriage return](https://bliptext.com/articles/carriage-return) character.\nFor ease of external editing of the source file, later versions of BASIC-PLUS also allowed the & character as a line continuation character.\nMultiple statements could be placed on a single line using : as the statement separator.\nThe system allowed tabs to be used as inline whitespace, and was used to make loops more clear, as in modern languages.\nComments used either the REM keyword or the !\ncharacter, as opposed to MS BASICs, which used REM and '.\n\n## Standard statements\nThe PRINT command divided the screen into regions 14 spaces wide, and the comma was used to move between these locations; 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\".\nINPUT allowed a prompt string to be specified, but used the semicolon to separate it rather than the comma; INPUT \"WHAT IS THE VALUE\";A.\nStrings could be delimited by single or double quotes.\nIn addition to the CHR and ASCII functions that converted single characters to and from string format, BASIC-PLUS also supported Dartmouth's CHANGE command.\nCHANGE iterated the string and returned each character's ASCII value as a slot in a numeric array.\nFor instance, CHANGE 'HELLO' TO X would return an array with the five ASCII codes, 110, 105, 114, 114, 105, in elements 1 through 5, and the number 5, the length of the string, in element 0.\nOne 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.\n\n## Statement modifiers\nBASIC-PLUS added the concept of \"statement modifiers\", [JOSS](https://bliptext.com/articles/joss)-like conditions that could be applied to any statement.\nFor 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.\nFOR loops worked as in other versions of BASIC, and the NEXT command could not be used in an expression to exit early.\nInstead, the UNTIL and WHILE keywords could be used to control early exits.\nFor 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.\nModifiers could also be used to build compact one-line loops, for instance, X=X+1 WHILE X , =, and <>.\nOne interesting addition was the == operator, for \"approximately equal\".\nThis would return true if the two numbers would be printed the same, that is, their six most significant digits were the same.\nLogical operators included the typical NOT A, 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.\nThe DIM statement could allocate one-dimensional and two-dimensional arrays of any of the three data types.\nThe range of subscripts always began with 0 (but MAT statements did not set elements in row 0 or column 0).\nThe language also included a number of MAT commands to work with the entire array (or MATrix).\nThe MAT READ command would fill the matrix with values in a DATA statement, MAT INPUT would fill the array with user-typed values, and MAT PRINT would print out the elements in a 1D or 2D format.\nMAT 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.\nTRN would transpose an entire matrix, and INV would invert it.\nAdditionally, +, -, and * could be used on matrixes, performing the associated matrix operation.\n\n## File processing\nThe 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).\nThey 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](https://bliptext.com/articles/memory-mapped-file).\nInstead, 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.\nThe CLOSE statement caused the buffer to be written back (if necessary) before closing the file.\nBecause no additional sectors were cached, accessing data in the \"wrong\" order could multiply the number of disk accesses.\nAdditional 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.\nVirtual 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 LSET and RSET.\n\n# Virtual machine\nBASIC-PLUS was not an interpreter but a [compile and go system](https://bliptext.com/articles/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.\nThese 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.\nThis 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.\nBASIC-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.\nThe system stored a user's program in two formats.\nOne was the editable source code in text format, created using the SAVE command and normally placed in a .BAS file.\nThe 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.\n\n# BASIC Plus 2\nA related product called **Basic Plus 2** (\"BP2\" or **BASIC-Plus-2**), was later developed by DEC to add additional features and increased performance.\nIt used true compilation into [threaded code](https://bliptext.com/articles/threaded-code) and wrote its output to object files compatible with the machine code object files produced by the assembler and other language systems.\nThese object files could be kept in libraries.\nA linker (the TKB, also known as the taskbuilder) then created executable files from object files and the libraries.\nTKB also supported overlays; this allowed individual routines to be swapped into the virtual address space as needed, overlaying routines not currently being used.\nAdditionally, 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.\n(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.\nUnlike BASIC-PLUS (which was only available on RSTS/E), BP2 was also available for the [RSX-11](https://bliptext.com/articles/rsx-11) operating system.\nBP2 programs were also more compatible with the later [VAX BASIC](https://bliptext.com/articles/vsi-basic-for-openvms).\n\n# Comparison to MS BASIC\nMicrosoft BASIC was patterned very closely on BASIC-PLUS.\nEarlier 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](https://bliptext.com/articles/commodore-pet) and [Commodore 64](https://bliptext.com/articles/commodore-64).\nThe 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.\nMS BASIC also lacked the matrix commands.\n\n# Citations","revisionCount":0},"hasMore":false,"nextCursor":null}

History