发信人: les (Walk the walk, talk the talk), 信区: DotNet
标 题: Re: 你们最不喜欢.net的什么？
发信站: BBS 未名空间站 (Fri Mar 9 15:35:10 2007)
hehe, we have a very good discussion here.
But it's not neccessary to focus too much on the specific word(Opaque,Safe
or Type safe).
I think people know about this tradeoff(Opaque/flexible) from day one.
Let's take a look what MSDN says:
Type Safety, Security, and Verifiability
Delegates are entirely opaque structures. There are no operations on
delegates except for a constructor, and methods to invoke the encapsulated
function. The code of even these methods is supplied by the runtime rather
than by the compiler. The runtime is able to guarantee the encapsulated
method has the correct signature. Since a delegate encapsulates an object
reference, it can rely on the metadata for this object to maintain types-
safety at runtime. That is the key to a delegate being typesafe and
A delegate can be considered a mechanism to indirectly invoke a method. Such
an invocation retains the semantics of the more conventional method
invocation, however, in that the method invocation is polymorphic, and it is
not possible to bypass any security demands on the actual method that gets
invoked. Security is not compromised when indirectly invoking methods
【 在 Deling (流浪歌手-爬爬死爬腰酸) 的大作中提到: 】
: again, you don't get it, this has nothing to do with type safety.
※ 来源:·BBS 未名空间站 http://mitbbs.com·[FROM: 192.168.]