6 ms·
> Multiple processes are involved, giving meaning to a byte stream. Maybe in the case of Erlang, but that's a fairly unique case. Smalltalk[1], and by extensio
by 9rx 2y ago
> Multiple processes are involved, giving meaning to a byte stream.
Maybe in the case of Erlang, but that's a fairly unique case. Smalltalk[1], and by extension Objective-C, do not pass messages across processes.
Languages don't normally concern themselves with that kind of thing at all. You can build distributed computing on top of languages (pretty much any language), but that's not a trait of the language and way beyond the topic at hand.
[1] Which is what matters most as OO was literally defined by the design of Smalltalk.
- igouy 2y ago1987 "The design and implementation of distributed Smalltalk" https://dl.acm.org/doi/10.1145/38765.38836 https://dl.acm.org/doi/10.1145/38765.38836 https://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/html/faqs/lang/oop/faq-doc-3.html https://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/html/... > do not pass messages across processes Except "The Smalltalk-80 system provides support for multiple independent processes with three classes named Process, ProcessorScheduler, and Semaphore. A Process represents a sequence of actions that can be carried out independently of the actions represented by other Processes." "Ch. 15 Multiple Independent Processes" 1983 "Smalltalk-80 The Language and its Implementation" https://rmod-files.lille.inria.fr/FreeBooks/BlueBook/Bluebook.pdf https://rmod-files.lille.inria.fr/FreeBooks/BlueBook/Blueboo...