2 ms·
"Messaging" is polymorphism in action and a way to describe it to people without headaches by concentrating on benefits and use-cases, instead of implementation
by bad_user 16y ago
"Messaging" is polymorphism in action and a way to describe it to people without headaches by concentrating on benefits and use-cases, instead of implementation details.
And to be a little pedantic -- virtual method calls in Java/C#/C++ are also messages.
What Alan Kay meant was that a static type system doesn't blend with the OOP he enabled in Smalltalk. Do you know why?
Because in OOP polymorphism, method-dispatching is late-bound. And being late-bound it makes absolute sense for the developer to be able to override the method-dispatching that's being done (by means of method_missing and other mechanisms). But that's directly at odds with the purpose of a static type system.
And btw, structural typing is not dynamic typing. It has the same problem as the one described above.