計算機專業(yè)畢業(yè)設(shè)計外文翻譯----托管代碼的優(yōu)點-展示頁
2025-05-26 17:37本頁面
【正文】 code without having to resort to COM interop. The piler raises an error if you attempt to use features that are not supported by .NET on managed types (for example, templates or multiple inheritance of classes). You will also find that you will need to use nonstandard C++ features (such as the __gc keyword shown in the previous code) when using managed classes. Because of the freedom that C++ allows in terms of lowlevel pointer manipulation and so on, the C++ piler is not able to generate code that will pass the CLR’s memory type safety tests. If it’s important that your code is recognized by the CLR as memory type safe, then you’ll need to write your source code in some other language (such as C or Visual Basic .NET). Visual J .NET The latest language to be added to the mix is Visual J .NET. Prior to .NET Framework , users were able to use J only after making a separate download. Now the J language is built into the .NET Framework. Because of this, J users are able to take advantage of all the usual features of Visual Studio .NET. Microsoft expects that most J++ users will find it easiest to use J if they want to work with .NET. Instead of being targeted at the Java runtime libraries, J uses the same base class libraries that the rest of the .NET pliant languages use. This means that you can use J for building Web applications, Windows Forms, XMLWeb services, and everything else that is possible— just as C and Visual Basic .NET can. Scripting languages Scripting languages are still around, although, in general, their importance is likely to decline with the advent of .NET. JScript, on the other hand, has been upgraded to JScript .NET. We can now write pages in JScript .NET, run JScript .NET as a piled rather than an interpreted language, and write strongly typed JScript .NET code. With there is no reason to use scripting languages in serverside Web pages. VBA is, however, still used as a language for Microsoft Office and Visual Studio macros. COM and COM+ Technically speaking, COM and COM+ aren’t technologies targeted at .NET, because ponents based on them cannot be piled into IL (although it’s possible to do so to some degree using managed C++, if the original COM ponent was written in C++). However, COM+ remains an important tool, because its features are not duplicated in .NET. Also, COM ponents will still work— and .NET incorporates COM interoperability features that make it possible for managed code to call up COM ponents and vice versa (this is discussed in Chapter 29). In general, however, you will probably find it more convenient for most purposes to code new ponents as .NET ponents, so that you can take
畢業(yè)設(shè)計相關(guān)推薦
鄂ICP備17016276號-1