Technically, this is not exactly true. Messages are propagated to superclasses if an objects has no receiver, so they are more messages than method calls.
Also, the design decisions were to make objects an isolated entities which communicate by message passing. They does not have implicit mailboxes like it is in Erlang, and are not strongly-isolated, share-nothing entities (which is what makes the whole system fault-tolerant).
However, objects are definitely has some concurrency, but no async features in modern terms.
> Messages are propagated to superclasses if an objects has no receiver, so they are more messages than method calls.
are they ? this could be implemented with simple vtables and function pointers, without any difference in the case of a function being present or not in the child class case
Technically, this is not exactly true. Messages are propagated to superclasses if an objects has no receiver, so they are more messages than method calls.
Also, the design decisions were to make objects an isolated entities which communicate by message passing. They does not have implicit mailboxes like it is in Erlang, and are not strongly-isolated, share-nothing entities (which is what makes the whole system fault-tolerant).
However, objects are definitely has some concurrency, but no async features in modern terms.