Lesson plan

FP (programming language)

FP (for functional programming) is a programming language created by John Backus to support the function-level programming paradigm. It allows building programs from a set of generally useful language primitives and avoiding named variables (a style also called tacit programming or "point free"). It was heavily influenced by APL developed by Kenneth E. Iverson in the early 1960s. The FP language was introduced in Backus's 1977 Turing Award paper, "Can programming be liberated from the von Neumann style?: a functional style and its algebra of programs". The paper sparked interest in functional programming research, eventually leading to modern functional languages, which are largely founded on the lambda calculus paradigm, and not the function-level paradigm Backus had hoped. In his Turing award paper, Backus described how the FP style is different: FP was used little beyond academia. In the 1980s, Backus created a successor language, FL, as an internal project at IBM Research.

Back to article

Article summary

FP (for functional programming) is a programming language created by John Backus to support the function-level programming paradigm. It allows building programs from a set of generally useful language primitives and avoiding named variables (a style also called tacit programming or "point free"). It was heavily influenced by APL developed by Kenneth E. Iverson in the early 1960s. The FP language was introduced in Backus's 1977 Turing Award paper, "Can programming be liberated from the von Neumann style?: a functional style and its algebra of programs". The paper sparked interest in functional programming research, eventually leading to modern functional languages, which are largely founded on the lambda calculus paradigm, and not the function-level paradigm Backus had hoped. In his Turing award paper, Backus described how the FP style is different: FP was used little beyond academia. In the 1980s, Backus created a successor language, FL, as an internal project at IBM Research.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.