<i id='fqGcy'><tr id='fqGcy'><dt id='fqGcy'><q id='fqGcy'><span id='fqGcy'><b id='fqGcy'><form id='fqGcy'><ins id='fqGcy'></ins><ul id='fqGcy'></ul><sub id='fqGcy'></sub></form><legend id='fqGcy'></legend><bdo id='fqGcy'><pre id='fqGcy'><center id='fqGcy'></center></pre></bdo></b><th id='fqGcy'></th></span></q></dt></tr></i><div id='fqGcy'><tfoot id='fqGcy'></tfoot><dl id='fqGcy'><fieldset id='fqGcy'></fieldset></dl></div>
    <tfoot id='fqGcy'></tfoot>

    <small id='fqGcy'></small><noframes id='fqGcy'>

      • <bdo id='fqGcy'></bdo><ul id='fqGcy'></ul>
      <legend id='fqGcy'><style id='fqGcy'><dir id='fqGcy'><q id='fqGcy'></q></dir></style></legend>
    1. 带委托的局部变量

      Local variables with Delegates(带委托的局部变量)

        <legend id='t2BHA'><style id='t2BHA'><dir id='t2BHA'><q id='t2BHA'></q></dir></style></legend>

          <small id='t2BHA'></small><noframes id='t2BHA'>

            <bdo id='t2BHA'></bdo><ul id='t2BHA'></ul>
            <tfoot id='t2BHA'></tfoot>
                <i id='t2BHA'><tr id='t2BHA'><dt id='t2BHA'><q id='t2BHA'><span id='t2BHA'><b id='t2BHA'><form id='t2BHA'><ins id='t2BHA'></ins><ul id='t2BHA'></ul><sub id='t2BHA'></sub></form><legend id='t2BHA'></legend><bdo id='t2BHA'><pre id='t2BHA'><center id='t2BHA'></center></pre></bdo></b><th id='t2BHA'></th></span></q></dt></tr></i><div id='t2BHA'><tfoot id='t2BHA'></tfoot><dl id='t2BHA'><fieldset id='t2BHA'></fieldset></dl></div>

                  <tbody id='t2BHA'></tbody>
              • 本文介绍了带委托的局部变量的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

                问题描述

                这个显然不是看起来不是最佳实践.有人可以解释为什么这不是最佳实践或它是如何工作的吗?任何提供解释的书籍或文章将不胜感激.

                This is clearly not appears like it wouldn't be a best practice. Can someone explain why it would not be a best practice or how this works? Any books or articles providing an explanation would be appreciated.

                //The constructor
                public Page_Index() {
                
                    //create a local value
                    string currentValue = "This is the FIRST value";
                
                    //use the local variable in a delegate that fires later
                    this.Load += delegate(object sender, EventArgs e) {
                        Response.Write(currentValue);
                    };
                
                    //change it again
                    currentValue = "This is the MODIFIED value";
                
                }
                

                输出的值是第二个值Modified".编译器魔术的哪一部分使这项工作起作用?这就像跟踪堆上的值并稍后再次检索它一样简单吗?

                The value that is output is the second value "Modified". What part of the compiler magic is making this work? Is this as simple as keeping track of the value on the heap and retrieving it again later?

                :给定一些评论,把原句改一下……

                : Given some of the comments, changing the original sentence some...

                推荐答案

                currentValue 不再是局部变量:它是一个捕获的 变量.这编译为:

                currentValue is no longer a local variable: it is a captured variable. This compiles to something like:

                class Foo {
                  public string currentValue; // yes, it is a field
                
                  public void SomeMethod(object sender, EventArgs e) {
                    Response.Write(currentValue);
                  }
                }
                ...
                public Page_Index() {
                  Foo foo = new Foo();
                  foo.currentValue = "This is the FIRST value";
                  this.Load += foo.SomeMethod;
                
                  foo.currentValue = "This is the MODIFIED value";
                }
                

                Jon Skeet 在 C# in Depth 中对此有很好的描述,另外还有一个 (没有那么详细)讨论这里.

                Jon Skeet has a really good write up of this in C# in Depth, and a separate (not as detailed) discussion here.

                请注意,变量 currentValue 现在位于堆上,而不是堆栈上 - 这有很多含义,尤其是它现在可以被各种调用者使用.

                Note that the variable currentValue is now on the heap, not the stack - this has lots of implications, not least that it can now be used by various callers.

                这与 java 不同:在 java 中,变量的 value 被捕获.在 C# 中,变量本身被捕获.

                This is different to java: in java the value of a variable is captured. In C#, the variable itself is captured.

                这篇关于带委托的局部变量的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

                本站部分内容来源互联网,如果有图片或者内容侵犯了您的权益,请联系我们,我们会在确认后第一时间进行删除!

                相关文档推荐

                Multicast delegate weird behavior in C#?(C# 中的多播委托奇怪行为?)
                Parameter count mismatch with Invoke?(参数计数与调用不匹配?)
                How to store delegates in a List(如何将代表存储在列表中)
                How delegates work (in the background)?(代表如何工作(在后台)?)
                C# Asynchronous call without EndInvoke?(没有 EndInvoke 的 C# 异步调用?)
                Delegate.CreateDelegate() and generics: Error binding to target method(Delegate.CreateDelegate() 和泛型:错误绑定到目标方法)
                  <bdo id='NIvvg'></bdo><ul id='NIvvg'></ul>
                • <tfoot id='NIvvg'></tfoot>
                      <tbody id='NIvvg'></tbody>
                  • <legend id='NIvvg'><style id='NIvvg'><dir id='NIvvg'><q id='NIvvg'></q></dir></style></legend>
                  • <small id='NIvvg'></small><noframes id='NIvvg'>

                          <i id='NIvvg'><tr id='NIvvg'><dt id='NIvvg'><q id='NIvvg'><span id='NIvvg'><b id='NIvvg'><form id='NIvvg'><ins id='NIvvg'></ins><ul id='NIvvg'></ul><sub id='NIvvg'></sub></form><legend id='NIvvg'></legend><bdo id='NIvvg'><pre id='NIvvg'><center id='NIvvg'></center></pre></bdo></b><th id='NIvvg'></th></span></q></dt></tr></i><div id='NIvvg'><tfoot id='NIvvg'></tfoot><dl id='NIvvg'><fieldset id='NIvvg'></fieldset></dl></div>