In object-oriented programming, delegation refers to evaluating a member (property or method) of one object (the receiver) in the context of another original object (the sender). Delegation can be done explicitly, by passing the responsibilities of the sending object to the receiving object, which can be done in any object-oriented language; or implicitly, by the member lookup rules of the language, which requires language support for the feature. Implicit delegation is the fundamental method for behavior reuse in prototype-based programming, corresponding to inheritance in class-based programming. The best-known languages that support delegation at the language level are Self, which incorporates the notion of delegation through its notion of mutable parent slots that are used upon method lookup on self calls, and JavaScript; see JavaScript delegation.
The term delegation is also used loosely for various other relationships between objects; see delegation (programming) for more. Frequently confused concepts are simply using another object, more precisely referred to as consultation or aggregation; and evaluating a member on one object by evaluating the corresponding member on another object, notably in the context of the receiving object, which is more precisely referred to as forwarding (when a wrapper object doesn't pass itself to the wrapped object). The delegation pattern is a software design pattern for implementing delegation, though this term is also used loosely for consultation or forwarding.
This sense of delegation as programming language feature making use of the method lookup rules for dispatching so-called self-calls was defined by Lieberman in his 1986 paper "Using Prototypical Objects to Implement Shared Behavior in Object-Oriented Systems".
Delegation is dependent upon dynamic binding, as it requires that a given method call can invoke different segments of code at runtime. It is used throughout macOS (and its predecessor NeXTStep) as a means of customizing the behavior of program components.[1] It enables implementations such as making use of a single OS-provided class to manage windows, because the class takes a delegate that is program-specific and can override default behavior as needed. For instance, when the user clicks the close box, the window manager sends the delegate a windowShouldClose: call, and the delegate can delay the closing of the window, if there is unsaved data represented by the window's contents.
Delegation can be characterized (and distinguished from forwarding) as late binding of self:[2] That is, the in a method definition in the receiving object is not statically bound to that object at definition time (such as compile time or when the function is attached to an object), but rather at evaluation time, it is bound to the original object.
It has been argued that delegation may in some cases be preferred to inheritance to make program code more readable and understandable.[3] Despite explicit delegation being fairly widespread, relatively few major programming languages implement delegation as an alternative model to inheritance. The precise relationship between delegation and inheritance is complicated; some authors consider them equivalent, or one a special case of the other.[4]
In languages that support delegation via method lookup rules, method dispatching is defined the way it is defined for virtual methods in inheritance: It is always the most specific method that is chosen during method lookup. Hence it is the original receiver entity that is the start of method lookup even though it has passed on control to some other object (through a delegation link, not an object reference).
Delegation has the advantage that it can take place at run time and affect only a subset of entities of some type and can even be removed at run time. Inheritance, by contrast, typically targets the type rather than the instances, and is restricted to compile time. On the other hand, inheritance can be statically type-checked, while delegation generally cannot without generics (although a restricted version of delegation can be statically typesafe[5]). Delegation can be termed "run-time inheritance for specific objects."
Here is a pseudocode example in a C#/Java like language:
class B
a = new A;b = new B(a); // establish delegation between two objects
Calling will result in b.bar being printed, since refers to the original receiver object,, within the context of . The resulting ambiguity of is referred to as object schizophrenia.
Translating the implicit into an explicit parameter, the call (in, with a delegate) translates to, using the type of for method resolution, but the delegating object for the argument.
Using inheritance, the analogous code (using capital letters to emphasize that resolution is based on classes, not objects) is:
class B extends A
b = new B;
Calling will result in B.bar. In this case, is unambiguous: there is a single object,, and resolves to the method on the subclass.
Programming languages in general do not support this unusual form of delegation as a language concept, but there are a few exceptions.
If the language supports both delegation and inheritance one can do dual inheritance by utilizing both mechanisms at the same time as in
This calls for additional rules for method lookup, as there are now potentially two methods that can be denoted as the most specific (due to the two lookup paths).
Delegation can be described as a low level mechanism for sharing code and data between entities. Thus it builds the foundation for other language constructs. Notably role-oriented programming languages have been utilizing delegation, but especially the older ones factually used aggregation while claiming to use delegation. This should not be considered cheating, merely the plural definitions of what delegation means (as described above).
More recently work has also been done on distributing delegation, so e.g. clients of a search engine (finding cheap hotel rooms) can use a shared entity using delegation to share best hits and general re-usable functionality.
Delegation has also been suggested for advice resolution in aspect-oriented programming by Ernst and Lorenz in 2003.
Distinguish:
. Henry Lieberman . Using prototypical objects to implement shared behavior in object-oriented systems . Conference proceedings on Object-oriented programming systems, languages and applications . ACM SIGPLAN Notices . 21 . 11 . Portland . 1986 . 214–223 . http://web.media.mit.edu/~lieber/Lieberary/OOP/Delegation/Delegation.html. 10.1145/960112.28718 . 10.1.1.48.69 .
. Erich Gamma . Richard Helm . Richard . Helm . Ralph Johnson (computer scientist) . Ralph . Johnson . John Vlissides . John . Vlissides . 1995 . Design Patterns: Elements of Reusable Object-Oriented Software . . 978-0-201-63361-0. Design Patterns (book) .
. Kent Beck . 1997 . Smalltalk Best Practice Patterns . Prentice Hall . 978-0134769042.