Erlang (programming language): Difference between revisions

Revision as of 02:02, 18 April 2023

Revision as of 15:22, 1 May 2023

Line 55:

Erlang applications are built of very lightweight Erlang processes in the Erlang runtime system. Erlang processes can be seen as "living" objects ([[object-oriented programming]]), with data encapsulation and [[message passing]], but capable of changing behavior during runtime. The Erlang runtime system provides strict [[process isolation]] between Erlang processes (this includes data and garbage collection, separated individually by each Erlang process) and transparent communication between processes (see [[Location transparency]]) on different Erlang nodes (on different hosts).

Joe Armstrong, co-inventor of Erlang, summarized the principles of processes in his [[Doctor of Philosophy|PhD]] [[thesis]]:<ref>http://erlang.org/download/armstrong_thesis_2003.pdf {{BareCite URLthesis |last=Armstrong |first=Joe |title=Making reliable distributed systems in the presence of software errors PDF|date=March20 November 2003 |degree=DTech |publisher=The Royal Institute of Technology |place=Stockholm, 2022Sweden}}</ref>

*Everything is a process.