The document defines the language piece by piece. For each part it defines the syntax and semantics. It also comments on the purpose for the part and gives examples of the code described. Good LRMs need examples, comments, syntax, and semantics.
This manual was written using XBNF and translated to HTML by Dr. Botting's mth2html translator that added the contents list and inserted hyperlinks. These are also parts of good manuals.
This is an example for a class and is the basis for project work, so I've not documented some of the options and issues that arise in the design languages. I've deliberately added one feature that is a bad idea. I wonder if you can spot the language that I ripped it from.... and added a perverse twist of my own. Finally I know of several typographical errors and many omissions.
This is a bad language. Do not try it at home. If you feel like
writing a compiler or interpreter don't --
it is not difficult BUT its better to fix the problems
with A FIRST. Your first job is to spot the problems and omissions.
A is not unlike half-a-dozen "autocodes" used in the 1960's in the United
Kingdom. Real languages in this family include: Pegasus Autocode, Elliott
803 Autocode, Mercury Autocode, and K-code. All were compiled, targeted
scientific computing, and are not mentioned in most text books. They did not
survive competition from FORTRAN, COBOL, and Algol. However, they are
small enough to be defined by a small LRM. A is slightly more complex than
Pegasus Autocode, and definitely less complex than K-code. The big
omission is any form data structure, and so, no indexing or
The Language A
Here is an example of a program written in A:
ENDThe above program reads a floating point decimal number (7.0 for example, and puts it into floating point location a. The next squares it, and stores the result in b. Then it prints out the result(49.0).
A program in A starts by executing the the first statement and finishes when the END statement is executed. Normally each statement is taken in sequence, however, some statements can select a different successor statement that is before or after them in the sequence. For example to print the sum of the first n integers one writes:
The following program does the same thing using a formula (s = n(n+1)/2) instead of a loop.
ENDNotice how complex formulas must be written out as a series of simple calculations.
d=d-eAn assignment evaluates the expression on the right hand side and places the value in the variable on the left hand side of the equals sign.
READ nWhen an input statement is executed a number (in decimal notation) is taken from the user and placed in the variable.
OUT Real RootsA PRINT statement evaluates its expression and converts it to decimal notation before sending it the the user. The OUT statement takes the text, as is, and send that that to the user.
SKIP +17*kSKIP statements are the only control statement. The break the flow of control. After a break statement control is passed to any statement before the or after the SKIP depending on the value of the expression in the SKIP. Notice that expressions can also evaluate simple tests by comparing values -- see Relations later.
The following indicates which statement is executed given the values 0, -1, -2, +1, and +2 in a SKIP:
(+2) ...It is possible to could any control flow using SKIP -- but a wise programmer will draw a flowchart first.
In expressions the values are converted from integers to floating point as needed.
The values of a relation are always either one(true) or zero(false). They
are typically used in SKIP statements to choose different successors
depending on the values of variable. For example the following code places
the larger of x and y into z.
z=xexercise: can you write code to put the minimum of x, y into z?
12.34Notice that "1." and ".95" must be written as "1.0" and "0.95" respectively.
OUT + or - i *
ENDExercise: handle the case when a is zero.
Here is an outline
of the semantic structure of the language A using the
A is not the smallest possible programming language.
. . . . . . . . . ( end of section The Language A) <<Contents | End>>
. . . . . . . . . ( end of section Language Reference Manual for the Language A) <<Contents | End>>