Actual advantage of Delegates ??

[anis_b]

Below is a valid example of a very simple Delegate.

Invocation is done at the line:

sd();

My Question is that whatever happens by calling "sd();"
can also be achieved by calling the "ActualFunction();"
Then WHY are we calling the other way round ??


using System;

namespace SimpleDelegateExample
{

delegate void SimpleDelegate();

class TestDelegate
{

static void ActualFunction()
{
Console.WriteLine("called by delegate..");
}

static void Main1()
{
SimpleDelegate sd = new SimpleDelegate(ActualFunction);
sd();
}

}

}

[Serge]

Delegates are always needed when you you use multithreaded applications. When you want to notify the control in the original thread, you will always have to use delegates.

[CornedBee]

My Question is that whatever happens by calling "sd();"
can also be achieved by calling the "ActualFunction();"

The interesting thing is that in a more complex application you don't know that it's ActualFunction you're calling. It might be MysteriousFunction or SecretFunction. It depends on what gets assigned to the delegate, and that's why they're useful.

If the situation makes it clear that it will always be ActualFunction that is called then you're misusing delegates.