3 ms·

https://en.wikipedia.org/wiki/Message_passing#Message_passing_versus_calling https://en.wikipedia.org/wiki/Message_passing#Message_passin...

• chrisseaton 8y ago
  This talks about primarily asynchronous message passing, which doesn't seem to be what anyone means in practice.
  • pjmlp 8y ago
    Actually that is how NeXT implemented distributed objects. http://www.nextop.de/NeXTstep_3.3_Developer_Documentation/GeneralRef/06_DistributedObjects/IntroDistObjects.htmld/index.html http://www.nextop.de/NeXTstep_3.3_Developer_Documentation/Ge...
    • chrisseaton 8y ago
      That document says that their messages were synchronous by default, and that asynchronous was something extra built on top just for distributed objects, not how they worked normally and not part of a uniform message passing interface.
      • pjmlp 8y ago
        Yes, it was up to you to change the behavior on doesNotUnderstand: methods, but the feature was available, just a matter of defaults.