为什么不能在 C# 的对象初始值设定项中分配事件和属性?这样做似乎很自然.
Why isn't it possible to assign events along with properties in object initializers in C#? It seems to be so natural to do so.
var myObject = new MyClass()
{
Property = value,
Event1 = actor,
// or
Event2 += actor
};
或者有什么我不知道的技巧?
Or is there some trick that I don't know of?
就外部合约而言,事件没有setter,只有add
和remove
methods - 订阅者可以从事件中注册和注销,publishing 对象通过引发"事件来决定何时调用回调.因此,分配事件"的想法通常是没有意义的.
As far the external contract is concerned, an event doesn't have a setter, only add
and remove
methods - subscribers can register and unregister from the event, and the publishing object decides when to invoke the callbacks by 'raising' the event. Consequently, the idea of "assigning an event", in general, is meaningless.
然而,当你在一个类中声明一个事件时,C# 编译器为你提供了一个真正方便的特性:当你不提供自己的实现时,它会创建一个private,为您提供支持委托字段,以及适当的添加/删除实现.这允许您在类内而不是在类外设置事件"(实际上是支持字段).要理解这一点,请考虑:
However, when you declare an event in a class, the C# compiler provides you with what is really a convenience-feature: when you don't provide your own implementation, it creates a private, backing delegate-field for you, along with the appropriate add / remove implementations . This allows you to "set the event" (really the backing field) within the class, but not outside it. To understand this, consider:
public class Foo
{
// implemented by compiler
public event EventHandler MyEvent;
public static Foo FooFactory(EventHandler myEventDefault)
{
// setting the "event" : perfectly legal
return new Foo { MyEvent = myEventDefault };
}
}
public class Bar
{
public static Foo FooFactory(EventHandler myEventDefault)
{
// meaningless: won't compile
return new Foo { MyEvent = myEventDefault };
}
}
public class Baz
{
// custom implementation
public event EventHandler MyEvent
{
add { } // you can imagine some complex implementation here
remove { } // and here
}
public static Baz BazFactory(EventHandler myEventDefault)
{
// also meaningless: won't compile
return new Baz { MyEvent = myEventDefault };
}
}
这篇关于在对象初始化器中分配事件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!