Editing Message passing (section)

==Mathematical models==
The prominent mathematical models of message passing are the [[Actor model]] and [[Pi calculus]].<ref>{{cite journal|last=Milner|first=Robin|title=Elements of interaction: Turing award lecture|journal=Communications of the ACM|date=Jan 1993|volume=36|issue=1|pages=78–89|doi=10.1145/151233.151240 |doi-access=free}}</ref><ref>{{Cite journal |last=Hewitt |first=Carl |last2=Bishop |first2=Peter |last3=Steiger |first3=Richard |date=1973-08-20 |title=A universal modular ACTOR formalism for artificial intelligence |url=https://dl.acm.org/doi/10.5555/1624775.1624804 |journal=Proceedings of the 3rd international joint conference on Artificial intelligence |series=IJCAI'73 |location=San Francisco, CA, USA |publisher=Morgan Kaufmann Publishers Inc. |pages=235–245}}</ref> In mathematical terms a message is the single means to pass control to an object. If the object responds to the message, it has a [[method (computer science)|method]] for that message.

[[Alan Kay]] has argued that message passing is more important than objects in OOP, and that objects themselves are often over-emphasized. The [[live distributed object]]s programming model builds upon this observation; it uses the concept of a [[distributed data flow]] to characterize the behavior of a complex distributed system in terms of message patterns, using high-level, functional-style specifications.<ref>{{cite web|last=Kay|first=Alan|title=prototypes vs classes was: Re: Sun's HotSpot|url=http://lists.squeakfoundation.org/pipermail/squeak-dev/1998-October/017019.html|work=lists.squeakfoundation.org|access-date=2 January 2014}}</ref>