Process-oriented programming: Difference between revisions

Revision as of 17:45, 27 June 2020

Revision as of 11:56, 21 September 2021

Line 4:

The paradigm was originally invented for parallel computers in the 1980s, especially computers built with [[transputer]] microprocessors by [[INMOS]], or similar architectures. [[Occam programming language|Occam]] was an early process-oriented language developed for the Transputer.

Some derivations have evolved from the [[message passing]] paradigm of Occam to enable uniform efficiency when porting applications between [[distributed memory]] and [[shared memory]] parallel computers {{Citation needed|date=June 2012}}. The first such derived example appears in the programming language [[Ease programming language|Ease]] designed at Yale University<ref name="process">{{cite paperdocument | last=Ericsson-Zenith | title=Programming with Ease; Semiotic definition of the language|publisher=Yale University, Computer Science Technical Report YALEU/DCS/RR-809|year=1990}}</ref><ref name="process2">{{cite book | last=Ericsson-Zenith |title=Process Interaction Models|publisher=Paris University|year=1992}}</ref> in 1990. Similar models have appeared since in the loose combination of SQL databases and objected oriented languages such as [[Java (programming language)|Java]], often referred to as object-relational models and widely used in large scale distributed systems today. The paradigm is likely to appear on desktop computers as microprocessors increase the number of processors ([[Multi-core processor|multicore]]) per chip.

The [[Actor model]] might usefully be described as a specialized kind of process-oriented system in which the message-passing model is restricted to the simple fixed case of one infinite [[input queue]] per process (i.e. actor), to which any other process can send messages.