Plankalkül

Not to be confused with Plan Calcul.

Plankalkül (German pronunciation: [ˈplaːnkalkyːl]) is a programming language designed for engineering purposes by Konrad Zuse between 1942 and 1945. It was the first high-level programming language to be designed for a computer.

Plankalkül

Paradigm	Procedural
Designed by	Konrad Zuse
First appeared	1948; 76 years ago (1948) – concept first published
Major implementations
Plankalkül-Compiler by the FU Berlin in 2000
Influenced
Superplan, ALGOL 58[1]

Kalkül (from Latin calculus) is the German term for a formal system—as in Hilbert-Kalkül, the original name for the Hilbert-style deduction system—so Plankalkül refers to a formal system for planning.^[2]

History of programming

In the domain of creating computing machines, Zuse was self-taught, and developed them without knowledge about other mechanical computing machines that existed already – although later on (building the Z3) being inspired by Hilbert's and Ackermann's book on elementary mathematical logic (see Principles of Mathematical Logic).^{[3]: 113, 152, 216} To describe logical circuits, Zuse invented his own diagram and notation system, which he called "combinatorics of conditionals" (German: Bedingungskombinatorik). After finishing the Z1 in 1938, Zuse discovered that the calculus he had independently devised already existed and was known as propositional calculus.^[4]: 3 What Zuse had in mind, however, needed to be much more powerful (propositional calculus is not Turing-complete and is not able to describe even simple arithmetic calculations^[5]). In May 1939, he described his plans for the development of what would become Plankalkül.^{[3]: 113, 152, 216} He wrote the following in his notebook:

Seit etwa einem halben Jahr allmähliches Einführen in die formale Logik. Viele meiner früheren Gedanken habe ich dort wiedergefunden. (Bedingungskombinatorik = Aussagenlogik; Lehre von den Intervallen = Gebietenkalkül). Ich plane jetzt die Aufsetzung des 'Plankalküls'. Hierzu sind eine Reihe von Begriffen zu klären.	Almost half a year of gradual introduction into formal logic. I rediscovered there lots of my previous thoughts. (combinatorics of conditionals = propositional calculus; study of intervals = lattice theory). I now plan the adoption of "Calculus of plans" onto this. A series of concepts need to be clarified for this.
	—Konrad Zuse's notebook[4]: 3

Historical marker on house in Hinterstein [de] where Zuse worked on Plankalkül

While working on his doctoral dissertation, Zuse developed the first known formal system of algorithm notation^[6]: 9 capable of handling branches and loops.^{[7]: 18 [3]: 56} In 1942 he began writing a chess program in Plankalkül.^{[3]: 216–217} In 1944, Zuse met with the German logician and philosopher Heinrich Scholz, who expressed appreciation for Zuse's utilization of logical calculus.^[8] In 1945, Zuse described Plankalkül in an unpublished book.^[9] The collapse of Nazi Germany, however, prevented him from submitting his manuscript.^[7]: 18

At that time the only two working computers in the world were ENIAC and Harvard Mark I, neither of which used a compiler, and ENIAC needed to be reprogrammed for each task by changing how the wires were connected.^[4]: 3

Although most of his computers were destroyed by Allied bombs, Zuse was able to rescue one machine, the Z4, and move it to the Alpine village of Hinterstein^[6]: 8 (part of Bad Hindelang).

The very first attempt to devise an algorithmic language was undertaken in 1948 by K. Zuse. His notation was quite general, but the proposal never attained the consideration it deserved.

— Heinz Rutishauser, creator of ALGOL

Unable to continue building computers – which was also forbidden by the Allied Powers^[10] – Zuse devoted his time to the development of a higher-level programming model and language.^[7]: 18 In 1948, he published a paper in the Archiv der Mathematik and presented at the Annual Meeting of the GAMM.^[3]: 89 His work failed to attract much attention.^{[citation needed]} In a 1957 lecture, Zuse expressed his hope that Plankalkül, "after some time as a Sleeping Beauty, will yet come to life."^[4]: 3 He expressed disappointment that the designers of ALGOL 58 never acknowledged the influence of Plankalkül on their own work.^{[7]: 18 [6]: 15}

Plankalkül was republished with commentary in 1972.^[11] The first compiler for Plankalkül was implemented by Joachim Hohmann in his 1975 dissertation.^[12] Other independent implementations followed in 1998^[13] and 2000 at the Free University of Berlin.^[4]: 2

Description

Plankalkül has drawn comparisons to the language APL, and to relational algebra. It includes assignment statements, subroutines, conditional statements, iteration, floating-point arithmetic, arrays, hierarchical record structures, assertions, exception handling, and other advanced features such as goal-directed execution. The Plankalkül provides a data structure called generalized graph (verallgemeinerter Graph), which can be used to represent geometrical structures.^[14]

Many features of the Plankalkül reappear in later programming languages; an exception is its idiosyncratic two-dimensional notation using multiple lines.

Some features of the Plankalkül:^[3]: 217

• only local variables
• functions do not support recursion
• only supports call by value
• composite types are arrays and tuples
• contains conditional expressions
• contains a for loop and a while loop
• no goto

Data types

The only primitive data type in the Plankalkül is a single bit or Boolean (German: Ja-Nein-Werte – yes-no value in Zuse's terminology). It is denoted by the identifier ${\displaystyle S0}$. All the further data types are composite, and build up from primitive by means of "arrays" and "records".^[15]: 679

So, a sequence of eight bits (which in modern computing could be regarded as byte) is denoted by ${\displaystyle 8\times S0}$, and Boolean matrix of size ${\displaystyle m}$ by ${\displaystyle n}$  is described by ${\displaystyle m\times n\times S0}$. There also exists a shortened notation, so one could write ${\displaystyle S1\cdot n}$ instead of ${\displaystyle n\times S0}$.^[15]: 679

Type ${\displaystyle S0}$ could have two possible values ${\displaystyle 0}$ and ${\displaystyle L}$. So 4-bit sequence could be written like L00L, but in cases where such a sequence represents a number, the programmer could use the decimal representation 9.^[15]: 679

Record of two components ${\displaystyle \sigma }$ and ${\displaystyle \tau }$ is written as ${\displaystyle (\sigma ,\tau )}$.^[15]: 679

Type (German: Art) in Plankalkül consists of 3 elements: structured value (German: Struktur), pragmatic meaning (German: Typ) and possible restriction on possible values (German: Beschränkung).^[15]: 679 User defined types are identified by letter A with number, like ${\displaystyle A1}$ – first user defined type.

Examples

Zuse used a lot of examples from chess theory:^[15]: 680

${\displaystyle A1}$	${\displaystyle S1\cdot 3}$	Coordinate of chess board (it has size 8x8 so 3 bits are just enough)
${\displaystyle A2}$	${\displaystyle 2\times A1}$	square of the board (for example L00, 00L denotes e2 in algebraic notation)
${\displaystyle A3}$	${\displaystyle S1\cdot 4}$	piece (for example, 00L0 — white king)
${\displaystyle A4}$	${\displaystyle (A2,A3)}$	piece on a board (for example L00, 00L; 00L0 — white king on e2)
${\displaystyle A5}$	${\displaystyle 64\times A3}$	board (pieces positions, describes which piece each of 64 squares contains)
${\displaystyle A10}$	${\displaystyle (A5,S0,S1\cdot 4,A2)}$	game state (${\displaystyle A5}$ — board, ${\displaystyle S0}$ — player to move, ${\displaystyle S1\cdot 4}$ — possibility of castling (2 for white and 2 for black), ${\displaystyle A2}$ — information about cell on which en passant move is possible

Identifiers

Identifiers are alphanumeric characters with a number.^[15]: 679 There are the following kinds of identifiers for variables:^[9]: 10

• Input values (German: Eingabewerte, Variablen) — marked with a letter V.
• Intermediate, temporary values (German: Zwischenwerte) — marked with a letter Z.
• Constants (German: Constanten) — marked with a letter С.
• Output values (German: Resultatwerte) — marked with a letter R.

Particular variable of some kind is identified by number, written under the kind.^[15]: 679 For example:

${\displaystyle {\begin{matrix}V\\0\end{matrix}}}$, ${\displaystyle {\begin{matrix}Z\\2\end{matrix}}}$, ${\displaystyle {\begin{matrix}C\\31\end{matrix}}}$ etc.

Programs and subprograms are marked with a letter P, followed by a program (and optionally a subprogram) number. For example ${\displaystyle P13}$, ${\displaystyle P5\cdot 7}$.^[15]: 679

Output value of program ${\displaystyle P13}$ saved there in variable ${\displaystyle {\begin{matrix}R\\0\end{matrix}}}$ is available for other subprograms under the identifier ${\displaystyle {\begin{matrix}R17\\0\end{matrix}}}$, and reading value of that variable also means executing related subprogram.^[15]: 680

Accessing elements by index

Plankalkül allows access for separate elements of variable by using "component index" (German: Komponenten-Index). When, for example, program receives input in variable ${\displaystyle {\begin{matrix}V\\0\end{matrix}}}$ of type ${\displaystyle A10}$ (game state), then ${\displaystyle {\begin{matrix}V\\0\\0\end{matrix}}}$ — gives board state, ${\displaystyle {\begin{matrix}V\\0\\0\cdot i\end{matrix}}}$ — piece on square number i, and ${\displaystyle {\begin{matrix}V\\0\\0\cdot i\cdot j\end{matrix}}}$ bit number j of that piece.^[15]: 680

In modern programming languages, that would be described by notation similar to V0[0], V0[0][i], V0[0][i][j] (although to access a single bit in modern programming languages a bitmask is typically used).

Two-dimensional syntax

Because indexes of variables are written vertically, each Plankalkül instruction requires multiple rows to write down.^{[citation needed]}

First row contains variable kind, then variable number marked with letter V (German: Variablen-Index), then indexes of variable subcomponents marked with K (German: Komponenten-Index), and then (German: Struktur-Index) marked with S, which describes variable type. Type is not required, but Zuse notes that this helps with reading and understanding the program.^[15]: 681

In the line ${\displaystyle S}$ types ${\displaystyle S0}$ and ${\displaystyle S1}$ could be shortened to ${\displaystyle 0}$ and ${\displaystyle 1}$.^[15]: 681

Examples:

${\displaystyle {\begin{array}{r|l}&V\\V&3\\K&\\S&m\times 2\times 1\cdot n\end{array}}}$	variable V3 — list of ${\displaystyle m}$ pairs of values of type ${\displaystyle S1\cdot n}$
${\displaystyle {\begin{array}{r|l}&V\\V&3\\S&m\times 2\times 1\cdot n\end{array}}}$	Row K could be skipped when it is empty. Therefore, this expression means the same as above.
${\displaystyle {\begin{array}{r|l}&V\\V&3\\K&i\cdot 0\cdot 7\\S&0\end{array}}}$	Value of eights bit (index 7), of first (index 0) pair, of і-th element of variable V3, has Boolean type (${\displaystyle S0}$).

Indexes could be not only constants. Variables could be used as indexes for other variables, and that is marked with a line, which shows in which component index would value of variable be used:

Z5-th element of variable V3. Equivalent to expression V3[Z5] in many modern programming languages.[15]: 681

Assignment operation

Zuse introduced in his calculus an assignment operator, unknown in mathematics before him. He marked it with «${\displaystyle \Rightarrow }$», and called it yields-sign (German: Ergibt-Zeichen). Use of concept of assignment is one of the key differences between mathematics and computer science.^[6]: 14

Zuse wrote that the expression:

${\displaystyle {\begin{array}{r|lll}&Z+1&\Rightarrow &Z\\V&1&&1\\\end{array}}}$

is analogous to the more traditional mathematical equation:

${\displaystyle {\begin{array}{r|lll}&Z+1&=&Z\\V&1&&1\\K&i&&i+1\\\end{array}}}$

There are claims that Konrad Zuse initially used the glyph as a sign for assignment, and started to use ${\displaystyle \Rightarrow }$ under the influence of Heinz Rutishauser.^[15]: 681 Knuth and Pardo believe that Zuse always wrote ${\displaystyle \Rightarrow }$, and that was introduced by publishers of «Über den allgemeinen Plankalkül als Mittel zur Formulierung schematisch-kombinativer Aufgaben» in 1948.^[6]: 14 In the ALGOL 58 conference in Zürich, European participants proposed to use the assignment character introduced by Zuse, but the American delegation insisted on :=.^[15]: 681

The variable that stores the result of an assignment (l-value) is written to the right side of assignment operator.^[6]: 14 The first assignment to the variable is considered to be a declaration.^[15]: 681

The left side of assignment operator is used for an expression (German: Ausdruck), that defines which value will be assigned to the variable. Expressions could use arithmetic operators, Boolean operators, and comparison operators (${\displaystyle =,\neq ,\leq }$ etc.).^[15]: 682

The exponentiation operation is written similarly to the indexing operation - using lines in the two-dimensional notation:^[9]: 45

Control flow

Boolean values were represented as integers with FALSE=0 and TRUE=1. Conditional control flow took the form of a guarded statement A -> B, which executed the block B if A was true. There was also an iteration operator, of the form W { A -> X; B -> Y} which repeats until all guards are false.^[16]

Terminology

Zuse called a single program a Rechenplan ("computation plan"). He envisioned what he called a Planfertigungsgerät ("plan assembly device"), which would automatically translate the mathematical formulation of a program into machine-readable punched film stock, something today would be called a translator or compiler.^{[3]: 45, 104, 105}

Example

The original notation was two-dimensional.^{[clarification needed]} For a later implementation in the 1990s, a linear notation was developed.

The following example defines a function max3 (in a linear transcription) that calculates the maximum of three variables:

P1 max3 (V0[:8.0],V1[:8.0],V2[:8.0]) → R0[:8.0]
max(V0[:8.0],V1[:8.0]) → Z1[:8.0]
max(Z1[:8.0],V2[:8.0]) → R0[:8.0]
END
P2 max (V0[:8.0],V1[:8.0]) → R0[:8.0]
V0[:8.0] → Z1[:8.0]
(Z1[:8.0] < V1[:8.0]) → V1[:8.0] → Z1[:8.0]
Z1[:8.0] → R0[:8.0]
END

See also

• History of programming languages
• Timeline of programming languages
• List of programming languages

References

1. Rojas, Raúl; Hashagen, Ulf [in German] (2002). The First Computers: History and Architectures. MIT Press. p. 292. ISBN 978-0-26268137-7. Retrieved 2013-10-25.
2. Zenil, Héctor [at Wikidata], ed. (2012). A Computable Universe: Understanding and Exploring Nature As Computation - with a Foreword by Sir Roger Penrose. Singapore: World Scientific Publishing Company. p. 791.
3. Hellige, Hans Dieter, ed. (January 2004) [November 2002]. Written at Bremen, Germany. Geschichten der Informatik. Visionen, Paradigmen, Leitmotive (in German) (1 ed.). Berlin / Heidelberg, Germany: Springer-Verlag. pp. 45, 56, 89, 104–105, 113, 152, 216–217. doi:10.1007/978-3-642-18631-8. ISBN 978-3-540-00217-8. ISBN 3-540-00217-0. (xii+514 pages)
4. Rojas, Raúl; Göktekin, Cüneyt; Friedland, Gerald; Krüger, Mike; Scharf, Ludmila; Kuniß, Denis; Langmack, Olaf (January 2004) [November 2002]. "Konrad Zuses Plankalkül — Seine Genese und eine moderne Implementierung" (PDF). In Hellige, Hans Dieter (ed.). Geschichten der Informatik. Visionen, Paradigmen, Leitmotive. Teil 3: Leitideen und Paradigmen in der Entwicklung der Programmiersprachen und der Programmierung (in German) (1 ed.). Berlin / Heidelberg, Germany: Springer-Verlag. pp. 215–235 [2–4]. doi:10.1007/978-3-642-18631-8_9. ISBN 978-3-642-62208-3. Archived from the original (PDF) on 2006-05-01. (21 [24] pages)
5. "Why is propositional logic not Turing complete?". Mathematics. StackExchange. 2013-04-01. Archived from the original on 2023-11-02. Retrieved 2023-11-02.
6. Knuth, Donald Ervin; Pardo, Luis Isidoro Trabb [in Portuguese] (August 1976). "The Early Development of Programming Languages" (PDF). Stanford University, Computer Science Department. pp. 8, 9, 14, 15. Archived from the original (PDF) on 2017-09-12. Retrieved 2017-12-28.
7. Giloi, Wolfgang K. [in German] (April–June 1997). "Konrad Zuse's Plankalkül: The First High-Level "non von Neumann" Programming Language". IEEE Annals of the History of Computing. 19 (2). IEEE: 17–24. doi:10.1109/85.586068. (8 pages)
8. Petzold, Hartmut [in German] (1992). Moderne Rechenkünstler. Die Industrialisierung der Rechentechnik in Deutschland (in German). München, Germany: C.H. Beck Verlag.
9. Zuse, Konrad (1946) [1945]. Rojas, Raúl; Wagner, G.; Scharf, Ludmila; Schöttker-Söhl [Schötke-Suhl], Susanne (eds.). Der Plankalkül (In der Fassung von 1945) (Manuscript) (in German). Konrad Zuse Internet Archive. pp. 10, 45. ZIA ID: 0233. Archived from the original on 2015-04-16. Retrieved 2023-11-01. (1+1+180 pages)
10. Coy, Wolfgang [in German] (January 2004) [November 2002]. "Was ist Informatik? Zur Entstehung des Faches an den deutschen Universitäten". In Hellige, Hans Dieter (ed.). Geschichten der Informatik. Visionen, Paradigmen, Leitmotive. Teil 5: Wandel der Leitkonzepte in der Wissenschaftsdisziplin Informatik (in German) (1 ed.). Berlin / Heidelberg, Germany: Springer-Verlag. pp. 473–498 [474]. doi:10.1007/978-3-642-18631-8_17. ISBN 978-3-540-00217-8. ISBN 3-540-00217-0.
11. Zuse, Konrad (1972). Der Plankalkül. Kommentierter Nachdruck der Fassung von 1945 (in German). Vol. 63. Sankt Augustin, Germany: Gesellschaft für Mathematik und Datenverarbeitung (GMD) / Bundesministerium für Bildung und Wissenschaft (BMBW). BMBW-GMD-63.
12. Hohmann, Joachim (1979). Der PLANKALKÜL im Vergleich mit algorithmischen Sprachen. Reihe Informatik und Operations Research (in German). Vol. 7 (1 ed.). Darmstadt, Germany: S. Toeche-Mittler-Verlag (stmv). ISBN 3-87820-028-5. (136 pages) Contents
13. Description of Plankalkül-Compiler by Wolfgang Mauerer; Mauerer, Wolfgang (2016-06-03). "Der Plankalkül von Konrad Zuse" (in German). Implementation in German. Archived from the original on 2016-06-03. Retrieved 2017-10-03.
14. Giloi, Wolfgang K. [in German] (November 1990), Konrad Zuses Plankalkül als Vorläufer moderner Programmiermodelle (in German)
15. Bauer, Friedrich L.; Wössner, Hans (1972). "The "Plankalkül" of Konrad Zuse: A Forerunner of Today's Programming Languages" (PDF). Communications of the ACM. 15 (7): 678–685. doi:10.1145/361454.361515. S2CID 17681101. Archived from the original (PDF) on 2009-02-20. (HTML)
16. Rojas, Raúl (2001). "Plankalkül" (PDF). Encyclopedia of computers and computer history. Chicago / London: Fitzroy Dearborn Publishers. p. 634. ISBN 1-57958235-4. Retrieved 2023-05-26.

Further reading

• Zuse, Konrad (1943). Ansätze einer Theorie des allgemeinen Rechnens unter besonderer Berücksichtigung des Aussagenkalküls und dessen Anwendung auf Relaisschaltungen [Inception of a universal theory of computation with special consideration of the propositional calculus and its application to relay circuits] (unpublished manuscript) (in German). Zuse Papers 045/018.
• Zuse, Konrad (1948-12-06) [November 1948]. Written at Hopferau bei Füssen, Germany. "Über den allgemeinen Plankalkül als Mittel zur Formulierung schematisch-kombinativer Aufgaben". Archiv der Mathematik (in German). 1 (6). Karlsruhe / Stuttgart / Basel, Germany: Birkhäuser Verlag: 441–449. doi:10.1007/BF02038459. eISSN 1420-8938. ISSN 0003-889X. (9 pages)
• Rojas, Raúl; Göktekin, Cüneyt; Friedland, Gerald; Krüger, Mike; Kuniß, Denis; Langmack, Olaf (February 2000). Plankalkül: The First High-Level Programming Language and its Implementation (PDF). Berlin, Germany: Institut für Informatik, Freie Universität Berlin & Feinarbeit.de. Technical Report B-3/2000. Archived from the original on 2006-05-01. (22 pages)
• Bruines, Bram (2010-01-08). "Plankalkül" (PDF) (Thesis). Archived (PDF) from the original on 2023-11-02. Retrieved 2023-11-02. (24 pages)

External links

• "Plankalkül-Programme". Konrad Zuse Internet Archive (in German and English). 2014-08-21. Archived from the original on 2014-08-21. Retrieved 2017-10-04. (NB. Plankalkül Java applets and documents.)