Template:Short description Template:About Template:Infobox programming language
TI BASIC is an ANSI-compliant interpreter for the BASIC programming language built into the 1979 Texas Instruments TI-99/4 home computer and its improved 1981 version, the TI-99/4A.
In contrast to most BASICs found on contemporary microcomputers, TI BASIC does not trace its history to Microsoft BASIC, but was instead developed in-house following the emerging Minimal BASIC standard being created by ANSI and ECMA. This was, in turn, based on the original Dartmouth BASIC from the 1960s. There are a number of differences, sometimes subtle, between TI BASIC and the more common MS varieties.
Minimal BASIC lacks a number of features that are commonly found on contemporary BASICs, and Texas Instruments later introduced the TI Extended BASIC cartridge that enhanced the functionality accessible to BASIC users. This included a wide variety of features found in other BASICs, as well as new system functions for sprite handling, sound, and other features of the platform.
As was common on home computers, TI BASIC was used not only for programming but also as a thin operating system. On top of Minimal BASIC, TI added commands for text, graphics, and basic file operations like recording to tape or any other file system. Due to the specifics of the TI-99 platform, TI BASIC was most notable for its extremely slow performance, roughly half that of common machines, but conversely sported high numerical accuracy.
PerformanceEdit
The TI-99 was based on the TMS9900 microprocessor, a 16-bit design that was originally built to provide a single-chip central processing unit (CPU) in low-end models of their TI-990 minicomputer lineup. The TMS9900 was also suitable for use in a microcomputer, but at that time the rest of the support chips required to build a complete computer were invariably 8-bit, and this included TI's wide catalog of such chips. In a minicomputer, 16-bit support systems were built up of many individual chips, but this was not suitable for a low-cost product. TI thus adopted the solution of making the machine mostly 8-bit and connecting the various support chips to this 8-bit bus, with the TMS9900 reading the bus twice to produce a 16-bit value.<ref name=arch>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>
The TMS9900's instruction set architecture was based on 16-bit opcodes, meaning that programs would generally be twice as large as they would be on an 8-bit machine. In the era of expensive memory, this presented a significant cost. To address this, TI created an 8-bit virtual machine with its own language or intermediate representation known as the "Graphic Programming Language", or GPL, that allowed programs to be written in a more compact format. The downside to this approach is that every GPL instruction had to be converted on the fly into one or more underlying TMS9900 instructions.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> The GPL code itself was stored on the 8-bit side of the machine, further slowing its performance.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>
For all of these reasons, the machine ran far slower than it was theoretically capable of. This was particularly noticeable in BASIC. Every instruction in the user's program had to be read from 8-bit memory, interpreted using code written in GPL, and then output back over the 8-bit bus again. As a result, TI BASIC had poor performance; on common benchmarks of the era, the TI-99 generally ran half as fast as 8-bit machines like the Commodore PET or Apple II.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> For instance, running the Byte Sieve in BASIC took 3960 seconds in TI BASIC, while the same test in Applesoft BASIC on the Apple II, ostensibly a much slower machine, took 2806 seconds, about 30% faster that the TI.<ref>Template:Cite magazine</ref>
Elements of TI BASICEdit
Editing and runningEdit
Unlike most BASICs of the era, TI BASIC did not provide a full-screen editor. Instead, a line editor was provided, which allowed the user to add or edit one line at a time. Explicit line numbers were used to order each statement. It used a <syntaxhighlight lang="text" class="" style="" inline="1">></syntaxhighlight> prompt to indicate the current new line in immediate mode, as opposed to the more common <syntaxhighlight lang="text" class="" style="" inline="1">READY</syntaxhighlight>.Template:Sfn Line numbers ranged from 1 to 32767, inclusive, and entering a line outside that range resulted in the "BAD LINE NUMBER" error.Template:Sfn Line entry was aided by the <syntaxhighlight lang="text" class="" style="" inline="1">NUMBER</syntaxhighlight> command, available only in immediate mode, which entered ascending line numbers,Template:Sfn and <syntaxhighlight lang="text" class="" style="" inline="1">RESEQUENCE</syntaxhighlight>, which renumbered an existing program.Template:Sfn
TI BASIC also included a number of debugging commands. <syntaxhighlight lang="text" class="" style="" inline="1">BREAK</syntaxhighlight> worked something like <syntaxhighlight lang="text" class="" style="" inline="1">STOP</syntaxhighlight>, stopping execution on certain lines. Unlike <syntaxhighlight lang="text" class="" style="" inline="1">STOP</syntaxhighlight>, the exit to immediate mode did not occur on the line where <syntaxhighlight lang="text" class="" style="" inline="1">BREAK</syntaxhighlight> appeared, but on the lines <syntaxhighlight lang="text" class="" style="" inline="1">BREAK</syntaxhighlight> referred to. For instance, <syntaxhighlight lang="text" class="" style="" inline="1">BREAK 130</syntaxhighlight> would cause the program to exit to immediate mode whenever it moved to line 130. This could be used, for example, by inserting a single <syntaxhighlight lang="text" class="" style="" inline="1">BREAK</syntaxhighlight> at the top of the program to control execution, rather than having to insert a <syntaxhighlight lang="text" class="" style="" inline="1">STOP</syntaxhighlight> in the middle of the code. <syntaxhighlight lang="text" class="" style="" inline="1">UNBREAK</syntaxhighlight> turned off existing breakpoints.Template:Sfn Additionally, <syntaxhighlight lang="text" class="" style="" inline="1">TRACE</syntaxhighlight> printed out the line number of the currently executing line in angle-brackets: <syntaxhighlight lang="text" class="" style="" inline="1"><100><110></syntaxhighlight> etc, and <syntaxhighlight lang="text" class="" style="" inline="1">UNTRACE</syntaxhighlight> turned it off.Template:Sfn
StatementsEdit
The ANSI-compatible statements of TI BASIC are Template:Mono
. Most of these operate in the same fashion as their MS counterparts with two additions; <syntaxhighlight lang="text" class="" style="" inline="1">RANDOMIZE</syntaxhighlight> restarts the random number generator at a given "seed" value, and <syntaxhighlight lang="text" class="" style="" inline="1">OPTION BASE</syntaxhighlight> sets the first entry in arrays to either 0 or 1, whereas MS is always zero-based. To this standard set it added CALL
, CLOSE
, DISPLAY
and OPEN
.Template:Sfn
In keeping with the Minimal BASIC standard,<ref>Template:Cite tech report</ref> <syntaxhighlight lang="text" class="" style="" inline="1">IF</syntaxhighlight> statements could only perform branches, they could not perform arbitrary statements as was common in almost every other BASIC of the era. For instance, code such as: Template:Sxhl is not valid in TI BASIC. Instead, this would have to be performed using multiple lines: Template:Sxhl This can easily lead to off-by-one errors if the conversion is not careful about changing the sense of the boolean comparison. TI BASIC did, however, support the <syntaxhighlight lang="text" class="" style="" inline="1">ELSE</syntaxhighlight> clause:Template:Sfn Template:Sxhl The <syntaxhighlight lang="text" class="" style="" inline="1">PRINT</syntaxhighlight> statement used colons to separate items on different lines, in addition to the more common comma or semicolon. This precluded its use as a statement separator, a concept that TI BASIC did not have.Template:Sfn This means a line can have only a single statement. Due to the way BASIC interpreters work, <syntaxhighlight lang="text" class="" style="" inline="1">GOTO</syntaxhighlight>-based loops can be sped up significantly by combining code onto a single line, which reduces the number of lines in the program and the corresponding amount of time needed to find a particular line number. This seemingly minor missing feature may result in much slower code, and adding this feature was part of TI Extended BASIC.
Extensions to the Minimal BASIC system were often not represented directly in BASIC, but were instead accessed via the <syntaxhighlight lang="text" class="" style="" inline="1">CALL</syntaxhighlight> command and a series of named GPL-based subroutines. For instance, <syntaxhighlight lang="text" class="" style="" inline="1">CALL CLEAR</syntaxhighlight> clears the screen, and <syntaxhighlight lang="text" class="" style="" inline="1">CALL KEY</syntaxhighlight> returns the keycode of the currently pressed key on the keyboard. The language lacked PEEK
and POKE
so there was no official way<ref>Exploit by James Abbatiello</ref> to create new CALLable code within BASIC, to do this one would require the TI Editor/Assembler, the TI Mini Memory cartridge which included a small assembler,<ref>{{#invoke:citation/CS1|citation
|CitationClass=web
}}</ref> or by using Extended BASIC.
FunctionsEdit
Unlike Microsoft BASICs, which used Template:Mono
, Template:Mono
, Template:Mono
, and Template:Mono
for manipulating strings, TI BASIC used the ANSI-compliant Template:Mono
and Template:Mono
.
- Template:Mono
- Absolute value
- Template:Mono
- ASCII numeric value of the first character of a string
- Template:Mono
- Arctangent
- Template:Mono
- Convert a number into a string with an ASCII character
- Template:Mono
- Cosine
- Template:Mono
- Test whether the end of a file has been reached
- Template:Mono
- Exponentiation
- Template:Mono
- greatest integer less than or equal to the parameter
- Template:Mono
- Length of a string
- Template:Mono
- Natural logarithm
- Template:Mono
- First occurrence of a string in another string
- Template:Mono
- Pseudorandom number generator
- Template:Mono
- Return a substring of a string
- Template:Mono
- Sign function
- Template:Mono
- Sine
- Template:Mono
- Square root
- Template:Mono
- Convert a number to a string
- Template:Mono
- Tangent
- Template:Mono
- Convert a string to a number
SubprogramsEdit
Subprograms are called with CALL
statement (e.g. CALL CLEAR
).
CHAR
Definition of graphical charactersCLEAR
Clears the screenCOLOR
Defines foreground- and background color for 8 charactersGCHAR
Reads one character at a specified position from the screenHCHAR
Writes a character to a screen position and repeats it horizontallyJOYST
Returns the position of the joystickKEY
Reads from the keyboard without echo on the screenSCREEN
Changes the color of the screenSOUND
Creates sounds (using a frequency) and noiseVCHAR
Writes a character to a screen position and repeats it vertically
Extended BASICEdit
TI BASIC was located in the system's internal ROMs. In 1981, TI released a plug-in ROM cartridge that added additional functions to the existing code, improving the language in a number of ways.Template:Sfn Known as Extended BASIC, it was a highly anticipated addition to the platform.<ref name=kaplan>Template:Cite magazine</ref>
Among the changes was the addition of the ability to have multiple statements on a line. Using multiple statements may improve performance; loops that are implemented in a single line run much faster. Additionally, statements could now span several lines. As the underlying dialect already used the colon for string separators, Extended BASIC used the double-colon for this purpose. Confusingly, as a statement with two colons was also possible in TI BASIC, for instance, <syntaxhighlight lang="text" class="" style="" inline="1">PRINT "A"::"B"</syntaxhighlight>, which would output "A", a blank line and then "B", so these statements required a space to be added in Extended BASIC, <syntaxhighlight lang="text" class="" style="" inline="1">PRINT "A": :"B"</syntaxhighlight>.Template:Sfn
Another overdue addition was that <syntaxhighlight lang="text" class="" style="" inline="1">IF</syntaxhighlight> statements could now perform arbitrary statements, rather than only a <syntaxhighlight lang="text" class="" style="" inline="1">GOTO</syntaxhighlight>. In Extended BASIC one could write a simple statement like <syntaxhighlight lang="basic" class="" style="" inline="1">IF X>10 THEN X=X-1</syntaxhighlight>. This also worked in the <syntaxhighlight lang="text" class="" style="" inline="1">ELSE</syntaxhighlight> clause, allowing statements like <syntaxhighlight lang="basic" class="" style="" inline="1">IF A=4 AND B=6 THEN R=10 ELSE PRINT "OOPS"</syntaxhighlight>.Template:Sfn
Other additions include a small selection of new statements, including <syntaxhighlight lang="text" class="" style="" inline="1">ACCEPT</syntaxhighlight>, <syntaxhighlight lang="text" class="" style="" inline="1">IMAGE</syntaxhighlight>, <syntaxhighlight lang="text" class="" style="" inline="1">LINPUT</syntaxhighlight>, <syntaxhighlight lang="text" class="" style="" inline="1">ON BREAK</syntaxhighlight>, <syntaxhighlight lang="text" class="" style="" inline="1">ON ERROR</syntaxhighlight>, <syntaxhighlight lang="text" class="" style="" inline="1">ON WARNING</syntaxhighlight>, <syntaxhighlight lang="text" class="" style="" inline="1">SUB</syntaxhighlight>, <syntaxhighlight lang="text" class="" style="" inline="1">SUBEND</syntaxhighlight> and <syntaxhighlight lang="text" class="" style="" inline="1">SUBEXIT</syntaxhighlight>. The last three statements are used for structured programming, allowing the creation of named subroutines. Extended BASIC also included a number of new functions and especially CALLable routines. Among the latter was a library of sprite commands, including ones that created motion that continued automatically.Template:Sfn
Speech synthesisEdit
When equipped with the TI Speech Synthesizer, TI Extended BASIC users could also generate speech from a predefined vocabulary as easily as writing text on-screen. For example, the following line of text would cause the speech synthesizer to identify the computer:Template:Sfn
CALL SAY("HELLO I AM A #TEXAS INSTRUMENTS# T I NINETY NINE FOUR A HOME COMPUTER")
Multi-word phrases are delimited with the # symbol, as #TEXAS INSTRUMENTS#
in this example. Using a word not included in the speech synthesizer's built-in vocabulary of 338 words and phrases would cause it to slowly spell out the word. TI's Terminal Emulator II cartridge provided text-to-speech functionality.Template:Sfn
ReferencesEdit
CitationsEdit
BibliographyEdit
External linksEdit
- Beginner's BASIC at ClassicCmp.org
- TI-99/4A BASIC Reference Card at ClassicCmp.org