The archives at theBentley Historical Library of the University of Michigan contain reference materials on the development of MAD and MAD/I, including three linear feet of printouts with hand-written notations and original printed manuals.[3][4][5][6]
MAD/I, an "extended" version of MAD for theIBM System/360 series of computers running under theMichigan Terminal System (MTS). Work on the new compiler started in 1965 as part of theARPA sponsored CONCOMP project at the University of Michigan. As work progressed it gradually became clear that MAD/I was a new language independent of the original 7090 version of MAD.[10]
GOM (Good Old MAD), a reimplementation of the original 7090 MAD for theIBM System/370 series of mainframe computers running theMichigan Terminal System (MTS). GOM was created in the early 1980s by Don Boettner at the University of Michigan Computing Center.[11][12]
WhileMAD was motivated byALGOL 58, it does not resemble ALGOL 58 in any significant way.[13][14]
Programs written in MAD included MAIL,[15]RUNOFF,[16] one of the first text processing systems, and several other utilities all underCompatible Time-Sharing System (CTSS).[17] Work was done on a design for a MAD compiler forMultics, but it was never implemented.[18]
The following is an interesting quote fromAn Interview withBrian Kernighan[19] when he was asked "What hooked you on programming?":
I think that the most fun I had programming was a summer job atProject MAC at MIT in the summer of 1966, where I worked on a program that created a job tape for the brand new GE 645 in the earliest days of Multics. I was writing in MAD, which was much easier and more pleasant than the FORTRAN and COBOL that I had written earlier, and I was using CTSS, the first time-sharing system, which was infinitely easier and more pleasant than punch cards.
MAD was quite fast compared to some of the other compilers of its day. Because a number of people were interested in using theFORTRAN language and yet wanted to obtain the speed of the MAD compiler, a system called MADTRAN (written in MAD) was developed. MADTRAN was simply a translator from FORTRAN to MAD, which then produced machine code. MADTRAN was distributed throughSHARE.[13]
MAD/I has a syntactic structure similar toALGOL 60 together with important features from the original MAD and fromPL/I.[10] MAD/I was designed as an extensible language. It was available for use underMTS and provided many new ideas which made their way into other languages, but MAD/I compilations were slow and MAD/I never extended itself into widespread use when compared to the original 7090 MAD.[12]
GOM is essentially the 7090 MAD language modified and extended for the 360/370 architecture with some judicious tailoring to better fit current programming practices and problems.[12] TheMTS Message System was written in GOM.
Line printer output following a MAD compiler error on an IBM 704 computer at the University of Michigan, c. 1960
In a pre-release version of the original MAD, as a reference to MAD's namesake,Mad magazine, when a program contained too many compile time errors the compiler would print a full-page picture ofAlfred E. Neuman usingASCII art. The caption read, "See this man about your program--He might want to publish it. He never worries--but from the looks of your program, you should."[9] This feature was not included in the final official version.[20] However, it was included in the production version for the IBM 7040.
And Bernie Galler remembers:
By the time we designed the language that we thought would be worth doing and for which we could do a compiler, we couldn't call it Algol anymore; it really was different. That's when we adopted the name MAD, for the Michigan Algorithm Decoder. We had some funny interaction with the Mad magazine people, when we asked for permission to use the name MAD. In a very funny letter, they told us that they would take us to court and everything else, but ended the threat with a P.S. at the bottom - "Sure, go ahead." Unfortunately, that letter is lost.[21]
The "hello, world" example program prints the string "Hello, world" to a terminal or screen display.
PRINT FORMAT HELLOWVECTOR VALUES HELLOW=$13h0Hello, world*$END OF PROGRAM
The first character of the line is treated aslogical carriage control, in this example the character "0" which causes a double-spaced line to be printed.
Alternatively, contractions can be used, and the compiler will expand them in the listing:
MAD programs are a series of statements written on punched cards, generally one statement per card, although a statement can be continued to multiple cards. Columns 1-10 contains an optional statement label, comments or remarks are flagged using the letter "R" in column 11, and columns 73-80 are unused and could contain a sequence identifier. Spaces are not significant anywhere other than within character constants. For GOM input is free form with no sequence field and lines may be up to 255 characters long; lines that start with an asterisk (*) are comments; and lines that start with a plus-sign (+) are continuation lines.
Variable names, function names, and statement labels have the same form, a letter followed by zero to five letters or digits. Function names end with a period. All names can be subscripted (the name followed by parentheses, with multiple subscripts separated by commas). For GOM names may be up to 24 characters long and may include the underscore (_) character.
Few keywords in the language are reserved words since most are longer than six letters or are surrounded by periods. There is a standard set of abbreviations which can be used to replace the longer words. These consist of the first and last letters of the keywords with an apostrophe between them, such as W'R for WHENEVER and D'N for DIMENSION.
MAD uses the term "mode" for its data types. Five basic modes are supported:
Integer written with or without a scale factor (1, +1, -1, 1K10, 1K) or as octal constants (to7777777777777K);
Floating Point written with or without an exponent (0., 1.5, -0.05, +100.4, -4., .05E-2, -.05E2, 5E02, 5.E2);
Boolean (1B for true and0B for false);
Statement Label, and
Function Name written as a name followed by a period (SQRT.).
The mode of a constant can be redefined by adding the character M followed by a single digit at the end of the constant, where 0 indicates floating point, 1 integer, 2 boolean, 3 function name, and 4 statement label.
For GOM six additional modes are added:CHARACTER, SHORT INTEGER, BYTE INTEGER, LONG INTEGER, POINTER, andDYNAMIC RECORD.
Alphabetic or character constants are stored as integers and written using the dollar sign as a delimiter ($ABCDEF$) with double dollar-signs used to enter a true dollar sign ($$$.56$ is 56 cents). Strings longer than six characters are represented using arrays.
Negative and zero as well as floating-point subscripts are allowed.
Matrices are storied in consecutive memory locations in the order determined by varying the rightmost subscript first.
Matrices may be referenced using a subscript for each dimension, NAME(s1,s2,s3), or using a single subscript, NAME(s1).
Input-output lists, VECTOR VALUES statements, and some subroutines allow the use of block notation, which has the form A,...,B or A...B, which is a reference to the entire region from A to B. inclusive. In terms of a vector, A(1)...A(N) would be A(1), A(2), A(3), ..., A(N).
There are facilities that allow changing dimensions at run-time; permitting the programmer to vary the location of the initial element in an array within the overall block which has been set aside for the array; and allowing an arbitrary storage mapping to be specified.
Variables may be implicitly or explicitly declared. By default all implicitly declared variables are assumed to be floating point. The NORMAL MODE IS statement may be used to change this default.
FLOATING POINT var1, var2, ... (may include dimension information)
INTEGER var1, var2, ... (may include dimension information)
BOOLEAN var1, var2, ... (may include dimension information)
FUNCTION NAMEname1,name2, ... (may include dimension information)
STATEMENT LABELlabel1,label2, ... (may include dimension information)
MODE NUMBERn, var1, var2, ... (may include dimension information)
NORMAL MODE IStype-name (INTEGER, BOOLEAN, FLOATING POINT, STATEMENT LABEL, or FUNCTION NAME)
NORMAL MODE IS MODE NUMBERn
DIMENSIONvariable(max-dimension) (declares an array from 0...max-dimension)
DIMENSIONvariable(from...to)
DIMENSIONvariable(subscript1,subscript2, ...,subscriptn) (declares a multidimensional array)
VECTOR VALUESarray(n) = c1, c2, c3, ...
VECTOR VALUESarray(m) ...array(n) = constant
DOUBLE STORAGE MODEmode-list (doubles the amount of storage allocated for the modes listed)
EQUIVALENCE (a1,a2, ...,am), ...
PROGRAM COMMONa,b,c, ... (may include dimension information)
ERASABLEa,b,c, ... (may include dimension information)
Function names end with a period. Internal and external functions are supported. Internal functions are compiled as part of the program in which they are used and share declarations and variables with the main program. External functions are compiled separately and do not share declarations and variables. A one statement definition of internal functions is permitted. Recursive functions are permitted, although the function must do some of the required saving and restoring work itself.
One of the most interesting features in MAD is the ability to extend the language by redefining existing operators, defining new operators, or defining new data types (modes). The definitions are made using MAD declaration statements and assembly language mnemonics included following the declaration up to the END pseudo-instruction that implement the operation.
MODE STRUCTUREmode-no =mode-noexisting-opmode-no SAME SEQUENCE ASmode-noexisting-opmode-no
where:
rank is one of SAME AS, LOWER THAN, or HIGHER THAN; and
mode-options are the options that appear on the MODE STRUCTURE statement.
Three pre-defined packages of definitions (MATRIX, DOUBLE PRECISION, and COMPLEX) are available for inclusion in MAD source programs using the INCLUDE statement.
^In August 2010 when asked about Jean's Sammet's statement that "MAD does not resemble ALGOL 58 in any significant way", Bruce Arden wrote: "Regarding Jean Sammet, she may have conflated the two versions of IAL (58 and60). Unlike the later version, the 58 version said nothing about what words (or language) should be used to identify conditional and transfer statements, which led for parsing reasons to words like WHENEVER. Also there were some additional features in MAD that went beyond the 58 specs."
^"... Doug McIlroy and Bob Morris wrote Multics runoff in BCPL based on Jerry Saltzer's MAD version of RUNOFF for CTSS.","Multics Software Features: Section 1.7.7", Multicans Web site. Retrieved November 10, 2018.
An Abbreviated description of the MAD compiler language,Fernando J. Corbató,Jerome H. Saltzer, Neil Barta, and Thomas N. Hastings, M.I.T. Computation Center Memorandum CC-213, June 1963.
CLSYS, a program to facilitate the use of the MAD translator for large (class-size) batches, Jerome H. Saltzer, M.I.T. Computation Center Memorandum CC-204. February 1963.
