Comments on: What’s The Point Of Delegates In .NET? http://lostechies.com/derickbailey/2008/10/09/what-s-the-point-of-delegates-in-net/ Better Than Yesterday Fri, 17 May 2013 03:30:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: derick.bailey http://lostechies.com/derickbailey/2008/10/09/what-s-the-point-of-delegates-in-net/#comment-13 derick.bailey Tue, 14 Oct 2008 20:03:57 +0000 /blogs/derickbailey/archive/2008/10/09/what-s-the-point-of-delegates-in-net.aspx#comment-13 @OJ The very nature of delegates will always be a delayed execution of the code they point to, no matter the intended use of the delegate. public void Foo(Action bar) { bar(); } or Action bar = new Action(someMethod); bar(); these are the most basic examples of using a delegate, and both of them are illustrations of delayed code execution - whether it's one wait cycle that is imperceptable by a human is irrelevant. The runtime is delaying the execution of the delegate's target until the delegate is invoked. @OJ

The very nature of delegates will always be a delayed execution of the code they point to, no matter the intended use of the delegate.

public void Foo(Action bar)
{
bar();
}

or

Action bar = new Action(someMethod);
bar();

these are the most basic examples of using a delegate, and both of them are illustrations of delayed code execution – whether it’s one wait cycle that is imperceptable by a human is irrelevant. The runtime is delaying the execution of the delegate’s target until the delegate is invoked.

]]> By: OJ http://lostechies.com/derickbailey/2008/10/09/what-s-the-point-of-delegates-in-net/#comment-12 OJ Tue, 14 Oct 2008 02:31:14 +0000 /blogs/derickbailey/archive/2008/10/09/what-s-the-point-of-delegates-in-net.aspx#comment-12 I think that your summation is PART of the answer, but not an answer as a whole. Delegates are used in scenarios where you are not delaying the execution of code, such as varying functionality based on state. I think that your summation is PART of the answer, but not an answer as a whole. Delegates are used in scenarios where you are not delaying the execution of code, such as varying functionality based on state.

]]> By: Maxim http://lostechies.com/derickbailey/2008/10/09/what-s-the-point-of-delegates-in-net/#comment-11 Maxim Fri, 10 Oct 2008 12:37:14 +0000 /blogs/derickbailey/archive/2008/10/09/what-s-the-point-of-delegates-in-net.aspx#comment-11 Never thought about the "delaying execution". Hummm thanks :) Never thought about the “delaying execution”. Hummm thanks :)

]]> By: Frank Quednau http://lostechies.com/derickbailey/2008/10/09/what-s-the-point-of-delegates-in-net/#comment-10 Frank Quednau Fri, 10 Oct 2008 06:22:14 +0000 /blogs/derickbailey/archive/2008/10/09/what-s-the-point-of-delegates-in-net.aspx#comment-10 Indeed, that characteristic of delegates came useful to an idea we are developing, which is basically a set of classes providing configuration APIs for setting up hierarchies of Windows Forms Controls. You don't really want to create the Control hierarchy when you are using the config API, instead delegates are set up in the proper way, and once the user calls the Setup(Control c) method all Action<Control> delegates created during the configuration can be executed. This also provides the advantage that youc an reuse such a Control Setup instance. Indeed, that characteristic of delegates came useful to an idea we are developing, which is basically a set of classes providing configuration APIs for setting up hierarchies of Windows Forms Controls. You don’t really want to create the Control hierarchy when you are using the config API, instead delegates are set up in the proper way, and once the user calls the Setup(Control c) method all Action delegates created during the configuration can be executed. This also provides the advantage that youc an reuse such a Control Setup instance.

]]>