3 ms·
It could even be expressed as `(params message receiver)`, or `message; <params>.{{receiver}}` or whatever other syntax. But it's going to be more thoughtful t
by rgoulter 5y ago
It could even be expressed as `(params message receiver)`, or `message; <params>.{{receiver}}` or whatever other syntax.
But it's going to be more thoughtful to explain what parts of programming or of software design or architecture are emphasised by different ways of arranging things.
`receiver.message(params)` puts an emphasis that it's the receiver which receives and acts upon the message. The receiver will conform to some kind of interface with which we can interact.
`sender.message(...)` seems completely bizarre to me. -- Some module's interaction with other things is where the interactions are defined? Sounds interesting if it works!
- bee_rider 5y agoHypothetically, you could design a language where methods aren't defined by the thing before the dot, but by the last argument, I guess? This doesn't seem like a very sensible thing to do, though.