3 ms·
It was the intent of Smalltalk, but not Simula, so it's not universal among the originators. Simula had actors implemented on top of objects and method calls, n
by int_19h 8y ago
It was the intent of Smalltalk, but not Simula, so it's not universal among the originators. Simula had actors implemented on top of objects and method calls, not the other way around.
But in practice, does it really make that much difference? A method call is really just a synchronous message. So at that point we're really talking about what messages objects should have - and looking at something like String, Array or Stream in Smalltalk, I don't see how it's substantially different from what we see in mainstream OO languages today.
- gambler 8y ago>A method call is really just a synchronous message. There is an important distinction. Messages are interpreted, at runtime. Which means you can do certain kinds of metaprogramming without getting outside of the normal tools of the language. This is not a black-and-white kind of thing, though. A method call can be more or less like a message depending on the language tooling provided.
- int_19h 8y agoThe tooling has also converged to some extent. Java is very much Simula-style, and methods calls aren't messages... except when they are: https://www.baeldung.com/java-dynamic-proxies https://www.baeldung.com/java-dynamic-proxies C# also has something similar with TransparentProxy, not to mention "dynamic".