|FactSnippet No. 1,542,928|
15 Facts About Integer BASIC
Integer BASIC was phased out in favor of Applesoft BASIC starting with the Apple II Plus in 1979.
|FactSnippet No. 1,542,929|
Integer BASIC added commands to read paddle controllers and over a series of quick edits had a version of the game up and running.
|FactSnippet No. 1,542,930|
Wozniak began work on back-porting the floating-point code into Apple Integer BASIC, but got sidetracked in the task of designing a floppy disk controller for what became the Disk II.
|FactSnippet No. 1,542,931|
Unlike later home computer platforms, Integer BASIC was not the default environment when the Apple I started, it normally started in the monitor.
|FactSnippet No. 1,542,932|
Integer BASIC included the AUTO command to automatically enter line numbers at a given starting number like AUTO 100, adding 10 to the last number with every new line.
|FactSnippet No. 1,542,933|
Integer BASIC's string handling was based on the system in HP BASIC.
|FactSnippet No. 1,542,934|
Strings in Integer Basic used a fixed amount of memory regardless of the number of characters used within them, up to a maximum of 255 characters.
|FactSnippet No. 1,542,935|
Integer BASIC included a TAB feature, which positioned the cursor on a given column from 0 to 39.
|FactSnippet No. 1,542,936|
Atari Integer BASIC supported the same command, while North Star Integer BASIC used EXIT.
|FactSnippet No. 1,542,937|
Integer BASIC ROMs included a machine code monitor, "mini-assembler", and disassembler to create and debug assembly language programs.
|FactSnippet No. 1,542,938|
Integer BASIC read the lines typed in by the user from a buffer and ran them through a parser which output a series of tokens.
|FactSnippet No. 1,542,939|
Some keywords were represented by multiple tokens; for instance, where Microsoft BASIC had one token for the keyword PRINT, Integer BASIC had three tokens: one if the keyword was followed by no arguments, one if followed by an arithmetic expression, and one if followed by a string literal.
|FactSnippet No. 1,542,940|
Integer BASIC programs requiring floating-point calculations could CALL into these routines.
|FactSnippet No. 1,542,941|
Integer BASIC processed more of the original source code into tokens, the runtime was faster than versions that required additional runtime parsing.
|FactSnippet No. 1,542,942|