Tu banner alternativo

SASL (programming language)

In this article we are going to analyze SASL (programming language) in detail, a topic that has gained great relevance in recent years. SASL (programming language) is a concept widely studied in various areas, from psychology to economics, including sociology and politics. Throughout history, SASL (programming language) has been the subject of debate and reflection by experts and academics, as well as public opinion in general. In this sense, it is of utmost importance to deepen the knowledge and understanding of SASL (programming language), in order to achieve a broader and clearer vision of its impact on society and daily life. Through this article, we propose to explore the multiple dimensions and facets of SASL (programming language), with the aim of enriching the debate and promoting critical reflection on this topic.

Tu banner alternativo
SASL
Paradigmfunctional
Designed byDavid Turner
First appeared1972 (1972)
Influenced by
ISWIM
Influenced
KRC, Miranda, Haskell

SASL (St Andrews Static Language, alternatively St Andrews Standard Language) is a purely functional programming language developed by David Turner at the University of St Andrews in 1972, based on the applicative subset of ISWIM.[1] In 1976 Turner redesigned and reimplemented it as a non-strict (lazy) language.[2] In this form it was the foundation of Turner's later languages Kent Recursive Calculator (KRC) and Miranda, but SASL appears to be untyped whereas Miranda has polymorphic types.

Burroughs Corporation used SASL to write a compiler and operating system.[3]

Notes

  1. ^ Turner, An implementation of SASL
  2. ^ Turner, A New Implementation Technique for Applicative Languages, pages 31-49
  3. ^ Turner, D. A. "Some History of Functional Programming Languages" (PDF).

References

  • Turner, D.A. "An Implementation of SASL". University of St. Andrews, Department of Computer Science Technical Report. TR/75/4.
  • Turner, D.A. (1979). "A New Implementation Technique for Applicative Languages". Software: Practice and Experience. 9: 31–49. doi:10.1002/spe.4380090105. S2CID 40541269.