5 ms·
then why the receiver would know too? There are more parties in this orgy: message receiver, message sender (method caller), environment (static: like imports),
by artemonster 2y ago
then why the receiver would know too? There are more parties in this orgy: message receiver, message sender (method caller), environment (static: like imports), context (dynamic: like stack). Why the heck of all of those the receiver decides?
- meheleventyone 2y agoI'd take all of those as receivers if they are reacting to a message being sent. To give another example in a game engine I recently worked on we sent messages between game entities and the sending entity could target itself directly and indirectly with no problems and a common pattern to keep components of the entity decoupled was to do just that. In some OOP languages the environment and everything else are all objects. I think Smalltalk itself works that way. Which reflects this way of thinking.