A TUTOR lesson consists of a sequence of ''units'' where each unit begins with the presentation of information and progress from one unit to the next is contingent on correctly answering one or more questions. As with [[COBOL]] paragraphs, control may enter a TUTOR unit from the preceding unit and exit into the next, but units are also callable as subroutines using the
Here is an example unit from page 5 of the ''TUTOR User's Memo'', March 1973 ([[Computer-based Education Research Laboratory]], University of Illinois at Urbana-Champaign):
unit math at 205 write Answer these problems 3 + 3 = 4 × 3 = arrow 413 answer 6 arrow 613 answer 12
Several things should be immediately apparent from this example.
writecommand above, the tag may consist of multiple lines. Continuation lines are either blank or have a leading tab.
What may not be apparent is the control structure implicit in this unit. The
arrow command marks the entrance to a ''judging block'' This control structure is one of TUTOR's unique features.
TUTOR contained a number of unique features. The following list is not intended as a substitute for a TUTOR manual, but merely highlights the most interesting, innovative, and sometimes confusing features of the language.
A ''judging block'' in TUTOR is a control structure that begins with an
arrow command and ends with the next
unit command. The
arrow command also prompts for input, with the special arrow character (resembling "▷") displayed as a prompt at the indicated screen coordinates. In effect, a judging block can be thought of as a backtracking control structure where the student may make multiple attempts to answer a question until a correct answer allows forward progress.
====Judging pattern matching====
Each judging block consists of a sequence of [[pattern matching]] commands, each of which introduces a (possibly empty) block of commands to be executed if that pattern matches. The two most common pattern matching commands were
wrong. These had identical pattern matching semantics except that
answer judged a student response to be correct if it matched, while
wrong judged a student response to be incorrect.
The tag fields on the
wrong commands consisted of lists of optional, required and alternative words. consider this example from exercise 4-1 in the 1973 ''TUTOR User's Memo'':
answer <it, is,a, it's, figure,
(right, rt) (triangle, triangular)
This would match answers such as "it is a right triangle" or "it's a triangular figure" or just "rt triangle". It would not match "sort of triangular" because the words "sort of" are not listed as ignored, and it would not match "triangle, right?" because the
order is wrong.
The pattern matching subsystem recognized spelling errors, so the words "triangel" or "triangl" would match the example pattern. The lesson author could use the
specs command to set how pedantic the system was about spelling errors.
The pattern matching algorithms used by various TUTOR implementations varied in detail, but typically, each word in the input text and each word in the pattern were converted to [[bit vector]]s. To see whether a word of student input matched a word of the pattern, the [[Hamming distance]] between the two bit vectors was used as a measure of the degree of difference between the words. Bit vectors were typically 60 or 64 bits long, with fields for letter presence, letter pair presence, and the first letter. As a result, the number of one bits in the [[exclusive or]] of two such bit vectors approximated the extent of the phonetic difference between the corresponding words. Tenczar and Golden, ''Spelling, Word and Concept Recognition'', Computer-Based Education Research Laboratory Rep. X-35, University of Illinois at Urbana, 1972.
====Judging control structures====
All early presentations of the control structure of a TUTOR judging block were confusing. In modern terms, however, a judging block can be described as an [[While loop|iterative control structure]] that exits when the student input is judged correct. The body
of this control structure consists of a series of [[Conditional (programming)#Case and switch statements|cases]], each introduced by a [[pattern matching]] command such as
wrong. All output produced by the body of the judging loop in the
previous cycle is erased from the screen prior to the next cycle.
Consider this example, from exercise 4-1 of the 1973 ''TUTOR User's Memo'':
wrong <it, is,a> square
write A square has four
In the event that the student inputs "square" or "a square", the answer is judged to be incorrect, and the text "A square has four sides." is output starting at line 15 column 1 on the screen. This output remains on the screen until the student begins to enter
a new answer, at which point, it is erased so that the response to the new answer can be computed. The mechanism by which the display screen rolls back to its previous state varies from implementation to implementation. Early implementations operated by switching the terminal into erase mode and re-executing the entire case that had matched. Some later implementations buffered the output produced during judging so that this output could be erased.
join command was a unique form of subroutine call. It was defined as being equivalent to textual substitution of the body of the joined unit in place of the join command itself (page 21, 1973 ''TUTOR User's Memo''). As such, a joined unit could contain part of a judging block. Thus, while the judging block is conceptually an [[While loop|iterator]] enclosing a series of [[Conditional (programming)#Case and switch statements|cases]], this block may be arbitrarily broken into subroutines. (An alternative subroutine call, the
do command, conformed to the usual semantics associated with subroutine calls in other programming languages.)
===Graphic and display commands===
The PLATO IV student terminal ''The Plato IV Student Terminal'' by Jack Stifle, Nov 1974 had a 512 by 512 [[pixel]] [[Plasma display|plasma display panel]],
with hardware support for [[point plotting]], line drawing, and text display.
Each pixel on the PLATO IV terminal was either orange or black. The CDC PLATO V terminal used a monochrome black and white [[Cathode ray tube|CRT]] to emulate the plasma panel. The built-in character set had 4 sets of 63 characters, each 8 by 16 pixels, half of these were fixed, half were programmable. The Tutor language provided complete support for this terminal.
There were two [[coordinate system]]s (see page II-1 of ''The TUTOR Language'' by Bruce Sherwood):
The following example illustrates some of Tutor's drawing commands. from page II-11 of ''The TUTOR Language'' by Bruce Sherwood, 1974.
Note the use of semicolons to separate successive coordinates on the
draw command. This allows unambiguous use of comma-separated fine coordinates. Normally, the draw command connects consecutive points with line segments, but by putting
skip in the tag, the
draw command could be made to conceptually lift its pen.
The tags on the
circle command give the radius and fine coordinates of the center. Additional tags could specify starting and
ending angles for partial circles.
Hand composing draw commands is difficult, so a picture editor was included in the PLATO system by 1974 to automate this work. see page II-9 of ''The TUTOR Language'' by Bruce Sherwood, 1974 This could only deal with drawing commands with constant coordinates.
====Text rendering commands====
The following example illustrates some of the text rendering tools of Tutor. from page II-3 of ''The TUTOR Language'' by Bruce Sherwood, 1974
size 9.5 $$ text 9.5 times normal size
rotate 45 $$ text rotated 45 degrees
size 0 $$ return to normal writing
write Lessons on Verbs
Text rendered in size zero rotation zero used the built-in character rendering hardware of the PLATO terminal, while rendering with nonzero size and rotation was done with line segments and therefore significantly slower due to the speed of the communication link to the terminal.
Aside from its unique answer judging mechanisms, TUTOR's original set of [[Control flow|control structures]] was rather sparse. In the mid 1970s, this shortcoming was addressed by introducing
endif blocks with optional
else sections. The semantics of these control structures was routine, but the syntax inherited the mandatory [[Indent style|indentation]] of the Tutor Language, presaging that of [[Python (programming language)|Python]] and adding a unique nonblank indent character to distinguish indenting from continuation lines.
This is illustrated in the following example, from page S5 of the ''Summary of TUTOR Commands and System Variables (10th ed)'' by [[Elaine Avner]], 1981:
. write first branch
. calc n9⇐34
. write second branch
. do someunit
. write default branch
. if n8>6
. . write special branch
(The [[Assignment (computer science)|assignment]] arrow in the
calc statement is not rendered correctly in some browsers. It appears similar to <= but as one character. It had a dedicated key on the PLATO IV keyboard.)
The same syntax was used for
endloop blocks with semantics comparable to [[while loop]]s in conventional programming languages. This is illustrated in the following example, from page S6 of the ''Summary of TUTOR Commands and System Variables (10th ed)'' by Elaine Avner, 1981:
. write within loop
. sub1 n8
. write still within loop
. do someunit
. write still within loop
write outside of loop
Note that the
outloop commands are somewhat analogous to the
break statements of languages based on [[C (programming language)|C]], except that they must sit at the indenting level of the loop they modify, and they have a condition tag that indicates when the indicated control transfer is to take place. This makes the construct more powerful that in other languages, because any line of the inner loop could terminate or reloop several outer loops with one statement.
TUTOR's expression syntax did not look back to the syntax of [[FORTRAN]], nor was it limited by poorly designed character sets of the era. For example, the PLATO IV character set included [[control characters]] for [[subscript and superscript]], and TUTOR used these for exponentiation. Consider this command (from page IV-1 of ''The TUTOR Language'', Sherwood, 1974):
The character set also included the conventional symbols for multiplication and division,
÷, but in a more radical departure from the conventions established by FORTRAN, it allowed implicit multiplication, so the expressions
3.4+5(23-3)/2 were valid, with the values 99 and 15.9, respectively (op cit). This feature was seen as essential. When students typed in a numeric answer to a question, they could use operators and variables and standard algebraic notation, and the program would use the TUTOR "compute" command to compile and run the formula and check that it was numerically equivalent (or within the floating point roundoff error) to the correct answer.
The language included a pre-defined constant named with the Greek letter pi (π), with the appropriate value, which could be used in calculations. Thus, the expression
πr2 could be used to calculate the area of a circle, using the built-in π constant, implicit multiplication and exponentiation indicated by a superscript.
In TUTOR, the floating-point comparison
x=y was defined as being true if
y were approximately equal (see page C5 of ''PLATO User's Memo, Number One'' by Avner, 1975). This simplified life for mathematically naïve developers of instructional lessons, but it occasionally caused headaches for developers of numerically sophisticated code because it was possible that both
x≥y could be true at the same time.
See page IX-3 of ''The TUTOR Language'' by Sherwood, 1974
As an authoring language, TUTOR began with only minimal memory resources and only the crudest tools for manipulating them. Each user process had a private data segment of 150 variables, and shared ''common blocks'' could be attached, allowing inter-user communication through shared memory.
On the PLATO IV system, words were 60 bits, in keeping with the [[CDC 6600]] family of computers. Some later implementations changed this to 64 bits. see ''Run Time Support of the TUTOR Language on a Small Computer System'' by [[Douglas W. Jones]]
====Basic memory resources====
The private memory region of each process consisted of 150 words each, referred to as student variables; the values of these variables were persistent, following the individual user from session to session. These were addressed as
n150 when used to hold integer values, or as
v150 when used to hold floating point values.
see pages IV-2 and IX-17 of ''The TUTOR Language'', Sherwood, 1974
A TUTOR lesson could attach a single region of up to 1500 words of shared memory using the
common command. Each lesson could have an unnamed temporary common block containing variables shared by all users of that lesson. Such blocks were created when a lesson came into use and deallocated when the lesson became inactive. In contrast, named common blocks were associated with a block of a lesson (a disk file). Shared memory was addressed as
nc1500 (for integers) or
vc1500 (for floating point numbers).
see pages X-1 to X-3 and X-6 of ''The TUTOR Language'', Sherwood, 1974
Where 150 student variables was insufficient, a lesson could use the
storage command to create an additional private memory segment of up to 1000 words. This segment existed in swap space only, but it could be mapped to student variables or common variables. For example (from page X-11 of ''The TUTOR Language'', Sherwood, 1974):
This example defines
nc1000 as a shared unnamed common block, while
nc1075 are private storage.
====Defining symbolic names====
define command was very similar to the [[C (programming language)|C]]
#define [[preprocessor]] directive. This was the only way to associate mnemonic names with variables. It was up to the programmer to statically allocate memory and assign names to variables. Consider this example from page 17 of the ''TUTOR User's Memo -- Introduction to TUTOR'', 1973"
first=v1, second =v2
This creates a set of definitions named
mynames defining three floating point variables. Users were advised that "there should not be any v3's or v26's anywhere in your lesson except in the
define statement itself. Put all your definitions at the very beginning of the lesson where you will have ready reference to which variables you are using." (underlining from the original, page IV-5 of ''The TUTOR Language'', Sherwood, 1974.)
Functions could be defined, with macro-substitution semantics, as in this illustration from page IX-2 of ''The TUTOR Language'', Sherwood, 1974:
Unlike C, the original [[scope (programming)|scope rules]] of TUTOR were pure "definition before use" with no provisions for local definitions. Thus, the formal parameter
a used above must not have any previous definition.
Later in the development of TUTOR, with the introduction of multiple named sets of definitions, the programmer was given explicit control over which sets of definitions were currently in force. For example,
define purge, setname would discard all definitions in the named set.
See page 15 of ''PLATO User's Memo -- Summary of TUTOR Commands and System Variables'', Avner, 1975
====Arrays, packed arrays, and text manipulation====
The original TUTOR tools for text manipulation were based on commands for specific text operations, for example,
pack to place a packed character string into consecutive variables in memory,
search to search for one string within another, and
move to move a string from memory to memory.
Pages VII-52 to VII-55 of ''The TUTOR Language'', Sherwood, 1974
By 1975, more general tools for arrays of integers and packed arrays were added. Page 14 of ''PLATO User's Memo -- Summary of TUTOR Commands and System Variables'', Avner, 1975, gives the following:
define segment, name=starting var, num bits per byte, s
array, name(size)=starting var
array, name (num rows, num columns)=starting var
''Segmented arrays'', defined with the keyword
segment, were comparable to packed arrays in [[Pascal (programming language)|Pascal]]. The byte size and whether or not the array elements were to be treated as signed or unsigned were entirely under user control. Arbitrary text manipulation could be done by setting the byte size to the machine byte size, 6 bits on implementations using [[display code]], 8 bits on some later [[ASCII]] and [[extended ASCII]] implementations. Note the lack of any specification of array dimensionality for segmented arrays.
A general [[Parameter (computer science)|parameter passing]] mechanism was added to TUTOR early in the PLATO IV era. Page IV-10 of ''The TUTOR Language'' by Sherwood, 1974 gives the following example:
unit halfcirc(radius, x,y)
circle radius, x,y,0,180
draw x-radius, y;x+radius, y
Notice that the [[Parameter (computer science)#Parameters and arguments|formal parameters]] listed in the argument list to the
unit command are simply the defined names for statically allocated global variables. The semantics of parameter passing was given as being equivalent to assignment at the time of the control transfer to the destination unit, and if [[Parameter (computer science)#Parameters and arguments|actual parameters]] were omitted, as in the second
do command above, the effect was to leave the prior values of the corresponding formal parameters unchanged.
Local variables were added to TUTOR some time around 1980. Lesson authors wishing to use local variables were required to use the
lvars command to declare the size of the buffer used for local variables, up to 128 words.
Page C3 of ''Summary of TUTOR Commands and System Variables'', Avner, 1981
Having done so, a unit using local variables could begin as follows (from Page C2 of ''Summary of TUTOR Commands and System Variables'', Avner, 1981):
``` unit someu NAME1,NAME2,NAME3(SIZE) NAME4=CONSTANT floating:NAME5,NAME6,NAME7(SIZE) integer, NUM BITS:NAME8,NAME9 integer, NUM BITS,signed:NAME10 integer:NAME11 ```
The continuation lines of the
unit command given above are taken to be lines of an implicit
define command with local [[Scope (programming)|scope]]. Conventional definitions in terms of student variables such as
n150 could be used in such a local
define, but the forms illustrated here all automatically bind names to locations in the block of memory allocated by the
lvars command. The available TUTOR documentation does not discuss how local variables are allocated.
There has been a sizable family of TUTOR-related languages, each similar to the original TUTOR language but with differences. In particular, TUTOR was a component of a system (the PLATO computer-based education system) that ran on particular CDC mainframe hardware. For efficiency, there were some hardware-specific elements in TUTOR (e.g. variables that were 60-bit words that could be used as arrays of 60 bits or as 10 six-bit characters, etc.). Also, TUTOR was designed before the advent of the windows-oriented graphical user interface (GUI).
The microTutor language was developed in the PLATO project at UIUC to permit portions of a lesson to run in terminals that contained microcomputers, with connections to TUTOR code running on the mainframe. The microTutor dialect was also the programming language of the Cluster system developed at UIUC and licensed to TDK in Japan; the Cluster system consisted of a small group of terminals attached to a minicomputer which provided storage and compilation. The [http://tencore.com Tencore Language Authoring System] is a TUTOR derivative developed by Paul Tenczar for PCs and sold by Computer Teaching Corporation. cT was a derivative of TUTOR and microTutor developed at Carnegie Mellon which allowed programs to run without change in windowed GUI environments on Windows, Mac, and Unix/Linux systems: [http://vpython.org/contents/cTsource/cToverview.html The cT Programming Language Archives]
Last modified 06 May 2021