使用委托有什么好处/优势?谁能提供一些简单的例子?
What are the benefits/advantages of using delegates? Can anyone provide any simple examples?
它们是封装一段代码的好方法.例如，当您将事件处理程序附加到按钮时，该处理程序就是委托.按钮不需要知道它的作用，只需要知道如何在正确的时间调用它.
They're a great way of encapsulating a piece of code. For instance, when you attach an event handler to the button, that handler is a delegate. The button doesn't need to know what it does, just how to call it at the right time.
另一个例子是 LINQ——过滤、投影等都需要相同类型的模板代码；所有的变化是表示过滤器、投影等的逻辑.使用 C# 3 中的 lambda 表达式(转换为委托或表达式树)，这使它变得非常简单:
Another example is LINQ - filtering, projecting etc all require the same kind of template code; all that changes is the logic to represent the filter, the projection etc. With lambda expressions in C# 3 (which are converted into delegates or expression trees) this makes it really simple:
var namesOfAdults = people.Where(person => person.Age >= 18)
.Select(person => person.Name);
(这也可以表示为查询表达式，但我们不要离委托太远.)
(That can also be represented as a query expression, but let's not stray too far from delegates.)
委托的另一种思考方式是作为单方法接口类型.例如，EventHandler 委托类型有点像:
Another way of thinking of a delegate is as a single-method interface type. For example, the EventHandler delegate type is a bit like:
public interface IEventHandler
{
void Invoke(object sender, EventArgs e)
}
但框架中的委托支持允许将委托链接在一起、异步调用、用作事件处理程序等.
But the delegate support in the framework allows delegates to be chained together, invoked asynchronously, used as event handlers etc.
有关代表和事件的更多信息，请参阅我关于该主题的文章.它的重点是事件，但也包括委托.
For more on delegates and events, see my article on the topic. Its focus is events, but it covers delegates too.
这篇关于代言人有什么好处?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！