计算机专业毕业外文翻译--托管代码的优点(编辑修改稿)

计算机专业毕业外文翻译--托管代码的优点(编辑修改稿)内容摘要：

n exits, so that it does not need to be repiled the next time that portion of code is run. Microsoft argues that this process is more efficient than piling the entire application code at the start, because of the likelihood that large portions of any application code will not actually be executed in any given run. Using the JIT piler, such code will never be piled. This explains why we can expect that execution of managed IL code will be almost as fast as executing native machine code. What it doesn’t explain is why Microsoft expects that we will get a performance improvement. The reason given for this is that, since the final stage of pilation takes place at runtime, the JIT piler will know exactly what processor type the program will run on. This means that it can optimize the final executable code to take advantage of any features or particular machine code instructions offered by that particular processor. Traditional pilers will optimize the code, but they can only perform optimizations that are independent of the particular processor that the code will run on. This is because traditional pilers pile to native executable before the software is shipped. This means that the piler doesn’t know what type of processor the code will run on beyond basic generalities, such as that it will be an x86patible processor or an Alpha processor. Visual Studio 6, for example, optimizes for a generic Pentium machine, so the code that it generates cannot take advantage of hardware features of Pentium III processors. On the other hand, the JIT piler can do all the optimizations that Visual Studio 6 can, and in addition it will optimize for the particular processor the code is running on. Language interoperability The use of IL not only enables platform independence。 it also facilitates language interoperability. Simply put, you can pile to IL from one language, and this piled code should then be interoperable with code that has been piled to IL from another language. You’re probably now wondering which languages aside from C are interoperable with .NET, so let’s briefly discuss how some of the other mon languages fit into .NET. Visual Basic .NET Visual Basic .NET has undergone a plete revamp from Visual Basic 6 to bring it uptodate with .NET. The way that Visual Basic has evolved over the last few years means that in its previous version, Visual Basic 6, it was not a suitable language for running .NET programs. For example, it is heavily integrated into COM and works by exposing only event handlers as source code to the developer— most of the background code is not available as source code. Not only that, it does not support implementation inheri。