4 ms·
That is probably because what he and we are talking about here is the technical definition of "delegation". If you just call a method of another object and the
by galaxyLogic 9y ago
That is probably because what he and we are talking about here is the technical definition of "delegation".
If you just call a method of another object and then that object perhaps but not necessarily sends some messages back to the original sender, to get further information, that could conceptually be seen as "delegation". But technically that's just normal (bi-directional) message-exchange.
"Delegation" needs to refer to something more technically specific to warrant its existence as a technical concept.
- josteink 9y agoFor languages which didn't have function-pointers as a first-class construct (like Java), you had to create another way to delegate functions between different objects. A way to encapsulate them, if you like. It may not seem novel now, but it was not obvious to everyone at that time that this was a possible design-pattern.