[kazinator]

That's a big down side of a framework for asynchronous message passing (object-oriented or not). E.g. "Flow based programming".

Message passing OOP doesn't necessarily imply that type of message passing. That is to say, the "send" call doesn't have to return until the target object has processed the message.

[onnoonno]

In a way, message passing using the usual way, methods, means TWO messages are passed: The parameters and the return value.

I think that obscures the better parts of the OOP view quite a bit.

[kazinator]

Also, method calls (that return) are really two calls, in a way: the call which passes the arguments along with a continuation, and then the call to the continuation which returns the value. :)