Term
|
Definition
Designer: Konrad Zuse
Date: 1936-1945
Simplest type was the bit; int and float types were built from the bit type; included arrays and records; no goto statement included; interative statement similar to Pascal for; included selection statement, but no else clause. |
|
|
Term
|
Definition
Designer: John Mauchly
Date: 1949
Designed for the BINAC computer, later transferred to the UNIVAC I; consisted of coded versions of mathematical expressions; variable were named with byte-pair codes, representing memory locations; interpreted language, took 50 times longer than machine code. |
|
|
Term
|
Definition
Designer: John Backus
Date: 1953
Pseudoinstructions for the four arithmetic operations on floating-point data; mathematical functions such as square root, sine, arc tangent, exponent, and logarithm; conditional and unconditional branches; input/output conversions |
|
|
Term
|
Definition
Designer: John Backus
Date: 1957
First widely accepted programming language; input/output formatting; variable names of up to six characters; user-defined subroutines (not separately compiled); if statement; do (loop) statement; all instructions based on IBM 704; no variable declarations; integer-type variables began with I, J, K, L, M, or N, all others were floating-point. |
|
|
Term
|
Definition
Designer: John McCarthy (MIT)
Date: 1958
Purely functional language; two data types: atoms and lists; all computations accomplished by applying functions to arguments; neither assignment statements nor variables are necessary in functional programs; recursive function calls can be used for iteration, making loops unnecessary. |
|
|
Term
|
Definition
Designer: ACM and GAMM
Date: 1958
Formalized the concept of data types; compound statements; allowed identifiers to have any length; allowed any number in array dimensions; programmer could specify lower bounds of arrays; selection statements could be nested. |
|
|
Term
|
Definition
Designer: DoD
Date: 1959
Based on English language; DEFINE verb, first high-level language construct for macros; heirarchical data structures; use of long names (30 characters) and word-connector characters (dashes); functions not supported; first language mandated by DoD. |
|
|
Term
BASIC
(Beginner's All-purpose Symbolic Instruction Code) |
|
Definition
Designers: John Kemeny and Thomas Kurtz
Date: 1964
Only 14 different statement types and a single data type; allowed program development from terminals connected to a computer; designed for both science and nonscience students. |
|
|
Term
|
Definition
Designer: IBM
Date: 1965
Originally called Fortran VI; attempt to combine business and science domains; used several features from different languages: recursion and block structure from ALGOL 60, separate compilation from Fortran IV, data structures and input/output from COBOL 60. |
|
|
Term
|
Definition
Designer: Kenneth E. Iverson
Date: 1960
Large number of operators; used Greek symbols not typically found on character maps; numerous array operations. |
|
|
Term
|
Definition
Designer: D. J. Farber,
R. E. Griswold, and F. P. Polensky
Date: early 1960s
Text processor with several powerful operations for string pattern matching; used for writing text editors. |
|
|
Term
|
Definition
| Reevaluated several features in ALGOL 60; introduced implicit heap-dynamic arrays, which can be declared without specific length and later determined at storage allocation; orthogonality. |
|
|
Term
|
Definition
Designers: Niklaus Wirth and Tony Hoare
Date: 1971
|
|
|
