Delegation (object-oriented programming) - Revision history

Logmanoriginal: Add wikilinks

2020-04-12T12:17:04Z

Add wikilinks

← Older revision		Revision as of 12:17, 12 April 2020
Line 1:		Line 1:
	In [[object-oriented programming]], '''delegation''' (sometimes referred to as ''delegation pattern'') allows one object (the ''delegate'') to operate on behalf of another object (the ''delegator'') without the need for a common ancestor. Instead of inheriting methods from a common ancestor, the delegator uses object composition to reuse functionality of the delegate. In programming languages that don't have native support for object delegation, the delegator may pass itself to the delegate to let it operate on behalf of the delegator. Alternatively, the delegator can keep an instance of the delegate in its private data and forward any delegate-specific behavior to it.		In [[object-oriented programming]], '''delegation''' (sometimes referred to as ''delegation pattern'') allows one [[object (object-oriented programming)\|object]] (the ''delegate'') to operate on behalf of another object (the ''delegator'') without the need for a common ancestor. Instead of [[Inheritance (object-oriented programming)\|inheriting]] methods from a common ancestor, the delegator uses [[composition (object-oriented programming)\|object composition]] to reuse functionality of the delegate. In programming languages that don't have native support for object delegation, the delegator may pass itself to the delegate to let it operate on behalf of the delegator. Alternatively, the delegator can keep an instance of the delegate in its private data and forward any delegate-specific behavior to it.

	==Use case example==		==Use case example==

Logmanoriginal: Clarify the need for the delegator to pass itself to the delegate

2020-04-12T12:12:43Z

Clarify the need for the delegator to pass itself to the delegate

← Older revision		Revision as of 12:12, 12 April 2020
Line 1:		Line 1:
	In [[object-oriented programming]], '''delegation''' (sometimes referred to as ''delegation pattern'') allows one object (the ''delegate'') to operate on behalf of another object (the ''delegator'') without the need for a common ancestor. Instead of inheriting methods from a common ancestor, the delegator uses object composition to reuse functionality of the delegate. In programming languages that don't have native support for object delegation, the delegator may pass itself to the delegate to let it operate on behalf of the delegator.		In [[object-oriented programming]], '''delegation''' (sometimes referred to as ''delegation pattern'') allows one object (the ''delegate'') to operate on behalf of another object (the ''delegator'') without the need for a common ancestor. Instead of inheriting methods from a common ancestor, the delegator uses object composition to reuse functionality of the delegate. In programming languages that don't have native support for object delegation, the delegator may pass itself to the delegate to let it operate on behalf of the delegator. Alternatively, the delegator can keep an instance of the delegate in its private data and forward any delegate-specific behavior to it.

	==Use case example==		==Use case example==

Logmanoriginal: Fix typos

2020-04-12T12:05:52Z

Fix typos

← Older revision		Revision as of 12:05, 12 April 2020
Line 1:		Line 1:
	In [[object-oriented programming]], '''delegation''' (sometimes referred to as ''delegation pattern'') allows one object (the ''delegate'') to operate on behalf of another object (the ''delegator'') without the need for a common ancestor. Instead of inheriting methods from a common ancestor, the delegator uses object composition to reuse functionality of the delegate. In programming languages that ~~doesn~~'t have native support for object delegation, the delegator may ~~passes~~ itself to the delegate to let it operate on behalf of the delegator.		In [[object-oriented programming]], '''delegation''' (sometimes referred to as ''delegation pattern'') allows one object (the ''delegate'') to operate on behalf of another object (the ''delegator'') without the need for a common ancestor. Instead of inheriting methods from a common ancestor, the delegator uses object composition to reuse functionality of the delegate. In programming languages that don't have native support for object delegation, the delegator may pass itself to the delegate to let it operate on behalf of the delegator.

	==Use case example==		==Use case example==

Logmanoriginal: Add new page

2020-04-12T12:03:59Z

Add new page

New page

In [[object-oriented programming]], '''delegation''' (sometimes referred to as ''delegation pattern'') allows one object (the ''delegate'') to operate on behalf of another object (the ''delegator'') without the need for a common ancestor. Instead of inheriting methods from a common ancestor, the delegator uses object composition to reuse functionality of the delegate. In programming languages that doesn't have native support for object delegation, the delegator may passes itself to the delegate to let it operate on behalf of the delegator.

==Use case example==
Classes ''Rectangle'', ''Square'', ''Circle'' and ''Triangle'' inherit from a common ancestor ''Surface'', which has a method ''Area'' to calculate the surface area.

<gallery mode="packed-overlay" widths=240px heights=240px>
File:Delegation - Example Main.png|Main VI
File:Delegation - Example Inheritance Hierarchy.png|Inheritance Hierarchy
</gallery>

After closer inspection, the formulas for ''Rectangle'', ''Square'' and ''Triangle'' are very similar and should reuse common functionality:

{| class="wikitable"
! Class
! Equation
|-
| Rectangle
| <code>a * b</code>
|-
| Square
| <code>a * a</code>
|-
| Triangle
| <code>a * b / 2</code>
|-
| Circle
| <code>PI*r^2</code>
|}

===Solution using inheritance===
''Square'' and ''Triangle'' inherit from ''Rectangle'', which implements the common functionality. In this case, ''Triangle'' needs to override the ''Area'' method in order to complete its equation.

<gallery mode="packed-overlay" widths=240px heights=240px>
File:Delegation - Example Using Inheritance - Inheritance Hierarchy.png|Inheritance Hierarchy
File:Delegation - Example Using Inheritance - Triangle overrides Rectangle.png|Triangle overrides Area method of Rectangle
</gallery>

This solution is considered bad practice, because ''Triangle'' is not a ''Rectangle''; the equation only happens to be based on rectangles. It also adds another layer of inheritance, which might not be desirable and can be problematic if classes require distinct behavior in the future.

===Solution using delegation===
''Square'' and ''Triangle'' use object composition to delegate some of their work to ''Rectangle''. In this case, both ''Square'' and ''Triangle'' keep their own instance of ''Rectangle'' in their private data and delegate any ''Rectangle''-specific behavior to it.

<gallery mode="packed-overlay" widths=240px heights=200px>
File:Delegation - Example Using Delegation - Square delegates to Rectangle.png|Square delegates its work to Rectangle
File:Delegation - Example Using Delegation - Triangle delegates to Rectangle.png|Triangle delegates its work to Rectangle
</gallery>

This solution requires extra work to implement, but if requirements change in the future, ''Rectangle'' can always be removed from either ''Square'' and ''Triangle'' without affecting any other classes.

==External links==
* [[Wikipedia:Delegation (object-oriented programming)|Delegation]] on Wikipedia
* [https://forums.ni.com/t5/LabVIEW-Development-Best/Delegation-Pattern/ta-p/3491604 Applying Common Object-Oriented Design Patterns to LabVIEW: Delegation Pattern] by Elijah Kerry

[[Category:Object-Oriented Programming]]
[[Category:Object-Oriented Design Pattern]]