計(jì)算機(jī)專業(yè)畢業(yè)設(shè)計(jì)外文翻譯----托管代碼的優(yōu)點(diǎn)-文庫(kù)吧
2025-04-16 17:37 本頁(yè)面
【正文】 ions 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 inheritance, and the standard data types Visual Basic 6 uses are inpatible with .NET. Visual Basic 6 was upgraded to Visual Basic .NET, and the changes that were made to the language are so extensive you might as well regard Visual Basic .NET as a new language. Existing Visual Basic 6 code does not pile as Visual Basic .NET code. Converting a Visual Basic 6 program to Visual Basic .NET requires extensive changes to the code. However, Visual Studio .NET (the upgrade of VS for use with .NET) can do most of the changes for you. If you attempt to read a Visual Basic 6 project into Visual Studio .NET, it will upgrade the project for you, which means that it will rewrite the Visual Basic 6 source code into Visual Basic .NET source code. Although this means that the work involved for you is heavily cut down, you will need to check through the new Visual Basic .NET code to make sure that the p
畢業(yè)設(shè)計(jì)相關(guān)推薦
鄂ICP備17016276號(hào)-1