News for hackers. Stuff that matters.
Re:A Healthy Hatred of OOP, or the principles of my message-... by daxfohl on Tuesday April 12, 2016 @11:26AM (#11480376)
The downside of message passing is debugging. No call stack so you can't trace things back to their source.
Re:A Healthy Hatred of OOP, or the principles of my message-... by SlipperySlope on Tuesday April 12, 2016 @11:37AM (#11480478)
An agent framework I built for my AI research has exactly that.

I use an additional message parameter, automatically inserted and maintained by the framework, which is a list of the messages (FIPA style operation + parameters) from the originating agent forwards to the point of debugging. This gets voluminous and is gated by debug levels.

Re:A Healthy Hatred of OOP, or the principles of my message-... by Diederich on Tuesday April 12, 2016 @01:05PM (#11481328)
Same here. The framework I've been building over and over for various companies for the past 20 years has extensive debugging capabilities. With the right 'messages all the way down' mindset, it gets extremely powerful.
Re:A Healthy Hatred of OOP, or the principles of my message-... by vidarh on Tuesday April 12, 2016 @01:06PM (#11481340)
Message passing in the OOP sense does not imply there's no call stack. Whether or not there's a call stack is an implementation detail.

The same holds true if you actually pass async messages on a bus - nothing stops you from attaching call details to the message. In fact, we have one very prominent async messaging system that does exactly that: E-mail (via "Received:" headers). (And yes, I've used e-mail as a message bus for applications before - Qmail worked great for that)

Re:A Healthy Hatred of OOP, or the principles of my message-... by mpweiher on Tuesday April 12, 2016 @12:17PM (#11480877)
Maybe we need better tools?

"Causeway, an open source distributed debugger written in E, lets you browse the causal graph of events in a distributed computation."

http://www.erights.org/elang/tools/causeway/index.html

Re:A Healthy Hatred of OOP, or the principles of my message-... by kazinator on Tuesday April 12, 2016 @12:19PM (#11480894)
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.

Re:A Healthy Hatred of OOP, or the principles of my message-... by onnoonno on Tuesday April 12, 2016 @03:24PM (#11482731)
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.

Re:A Healthy Hatred of OOP, or the principles of my message-... by kazinator on Tuesday April 12, 2016 @04:15PM (#11483173)
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. :)
Re:A Healthy Hatred of OOP, or the principles of my message-... by koder2016 on Tuesday April 12, 2016 @11:59AM (#11480689)
If the framework is factored well, then you can plug-in a synchronous single-threaded message delivery when debugging.