毕业论文外文翻译-C#.doc

《毕业论文外文翻译-C#.doc》由会员分享，可在线阅读，更多相关《毕业论文外文翻译-C#.doc（9页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、Where C# Fits InIn one sense, C# can be seen as being the same thing to programming languages as .NET is to the Windows environment. Just as Microsoft has been adding more and more features to Windows and the Windows API over the past decade, Visual Basic and C+ have undergone expansion. Although Vi

2、sual Basic and C+ have ended up as hugely powerful languages as a result of this, both languages also suffer from problems due to the legacies of how they have evolved.In the case of Visual Basic 6 and earlier, the main strength of the language was the fact that it was simple to understand and didnt

3、 make many programming tasks easy, largely hiding the details of the Windows API and the COM component infrastructure from the developer. The downside to this was that Visual Basic was never truly object-oriented, so that large applications quickly become disorganized and hard to maintain. As well a

4、s this, because Visual Basics syntax was inherited from early versions of BASIC (which, in turn, was designed to be intuitively simple for beginning programmers to understand, rather than to write large commercial applications), it didnt really lend itself to well-structured or object-oriented progr

5、ams.C+, on the other hand, has its roots in the ANSI C+ language definition. It isnt completely ANSIcompliant for the simple reason that Microsoft first wrote its C+ compiler before the ANSI definition had become official, but it comes close. Unfortunately, this has led to two problems. First, ANSI

6、C+ has its roots in a decade-old state of technology, and this shows up in a lack of support for modern concepts (such as Unicode strings and generating XML documentation), and in some archaic syntax structures designed for the compilers of yesteryear (such as the separation of declaration from defi

7、nition of member functions). Second, Microsoft has been simultaneously trying to evolve C+ into a language that is designed for high-performance tasks on Windows, and in order to achieve that theyve been forced to add a huge number of Microsoft-specific keywords as well as various libraries to the l

8、anguage. The result is that on Windows, the language has become a complete mess. Just ask C+ developers how many definitions for a string they can think of: char*, LPTSTR, string, CString (MFC version), CString (WTL version), wchar_t*, OLECHAR*, and so on.Now enter .NETa completely new environment t

9、hat is going to involve new extensions to both languages. Microsoft has gotten around this by adding yet more Microsoft-specific keywords to C+, and by completely revamping Visual Basic into Visual Basic .NET, a language that retains some of the basic VB syntax but that is so different in design tha

10、t we can consider it to be, for all practical purposes, a newlanguage. Its in this context that Microsoft has decided to give developers an alternativea language designed specifically for .NET, and designed with a clean slate. Visual C# .NET is the result. Officially, Microsoft describes C# as a “si

11、mple, modern, object-oriented, and type-safe programming language derived fromC and C+.” Most independent observers would probably change that to “derived from C, C+, and Java.” Such descriptions are technically accurate but do little to convey the beauty or elegance of the language. Syntactically,

12、C# is very similar to both C+ and Java, to such an extent that many keywords are the same, and C# also shares the same block structure with braces () to mark blocks of code, and semicolons to separate statements. The first impression of a piece of C# code is that it looks quite like C+ or Java code.

13、 Behind that initial similarity, however, C# is a lot easier to learn than C+, and of comparable difficulty to Java. Its design is more in tune with modern developer tools than both of those other languages, and it has been designed to give us, simultaneously, the ease of use of Visual Basic, and th

14、e highperformance, low-level memory access of C+ if required. Some of the features of C# are: Full support for classes and object-oriented programming, including both interface and implementationinheritance, virtual functions, and operator overloading. A consistent and well-defined set of basic type

15、s. Built-in support for automatic generation of XML documentation. Automatic cleanup of dynamically allocated memory. The facility to mark classes or methods with user-defined attributes. This can be useful for documentationand can have some effects on compilation (for example, marking methods to be

16、compiled only in debug builds). Full access to the .NET base class library, as well as easy access to the Windows API (if youreally need it, which wont be all that often). Pointers and direct memory access are available if required, but the language has been designedin such a way that you can work w

17、ithout them in almost all cases. Support for properties and events in the style of Visual Basic. Just by changing the compiler options, you can compile either to an executable or to a library of.NET components that can be called up by other code in the same way as ActiveX controls(COM components). C

18、# can be used to write ASP.NET dynamic Web pages and XMLWeb services.Most of the above statements, it should be pointed out, do also apply to Visual Basic .NET and Managed C+. The fact that C# is designed from the start to work with .NET, however, means that its support for the features of .NET is b

19、oth more complete, and offered within the context of a more suitable syntax thanfor those other languages. While the C# language itself is very similar to Java, there are some improvements:in particular, Java is not designed to work with the .NET environment.Before we leave the subject, we should po

20、int out a couple of limitations of C#. The one area the language is not designed for is time-critical or extremely high performance codethe kind where you really are worried about whether a loop takes 1,000 or 1,050 machine cycles to run through, and you need to clean up your resources the milliseco

21、nd they are no longer needed. C+ is likely to continue to reign supreme among low-level languages in this area. C# lacks certain key facilities needed for extremely high performance apps, including the ability to specify inline functions and destructors that are guaranteed to run at particular point

22、s in the code. However, the proportions of applications that fall into this category are very low.出处：Professional C#Third Edition作者：Simon RobinsonChristian NagelJay GlynnMorgan SkinnerKarli WatsonBill EvjenC#C#在某种程度上可以看作是.NET面向Windows环境的一种编程语言。在过去的十几年里，Microsoft给Windows和 Windows API添加了许多功能，VB和C+也经历了

23、许多变化。虽然VB和C+最终已成为非常强大的语言，但这两种语言也存在问题，因为它们保留了原来的一些内容。对于Visual Basic来说，它的主要优点是很容易理解，许多编程工作都很容易完成，基本上隐藏了Windows API和COM组件结构的内涵。其缺点是Visual Basic从来没有实现真正意义上的面向对象，所以大型应用程序很难分解和维护。另外，因为VB的语法继承于BASIC的早期版本(BASIC主要是为了让初学者更容易理解，而不是为了编写大型商业应用程序)，所以不能真正成为结构化或面向对象的编程语言。另一方面，C+在ANSI C+语言定义中有其自己的根。它与ANSI不完全兼容，因为Mic

24、rosoft是在ANSI定义标准化之前编写C+编译器的，但已经相当接近了。遗憾的是，这导致了两个问题。其一，ANSI C+是在十几年前的技术条件下开发的，因此不支持现在的概念(例如Unicode字符串和生成XML文档)，某些古老的语法结构是为以前的编译器设计的(例如成员函数的声明和定义是分开的)。其二，Microsoft同时还试图把C+演变为一种用于在Windows上执行高性能任务的语言 在语言中避免添加大量Microsoft专用的关键字和各种库。其结果是在Windows中，该语言成为了一种非常杂乱的语言。让一个C+开发人员说说字符串有多少个定义方式就可以说明这一点：char*、LPTSTR、

25、string、CString (MFC 版本)、CString (WTL 版本)、wchar_t*和 OLECHAR*等。现在进入.NET时代 一种全新的环境，它对这两种语言都进行了新的扩展。Microsoft给C+添加了许多Microsoft专用的关键字，并把VB演变为VB.NET，保留了一些基本的VB语法，但在设计上完全不同，从实际应用的角度来看，VB.NET是一种新语言。在这里，Microsoft决定给开发人员另一个选择 专门用于.NET、具有新起点的语言， 即Visual C# .NET。Microsoft在正式场合把C#描述为一种简单、现代、面向对象、类型非常安全、派生于C和C+的编

26、程语言。大多数独立的评论员对其说法是“派生于C、 C+ 和Java”。这种描述在技术上是非常准确的，但没有涉及到该语言的真正优点。从语法上看，C#非常类似于C+和Java，许多关键字都是相同的，C#也使用类似于C+和Java的块结构，并用括号()来标记代码块，用分号分隔各行语句。对C#代码的第一印象是它非常类似于C+或Java代码。但在这些表面上的类似性后面，C#学习起来要比C+容易得多，但比Java难一些。其设计与现代开发工具的适应性要比其他语言更高，它同时具有Visual Basic的易用性、高性能以及C+的低级内存访问性。C#包括以下一些特性： 完全支持类和面向对象编程，包括接口和继承、

27、虚函数和运算符重载的处理。 定义完整、一致的基本类型集。 对自动生成XML文档说明的内置支持。 自动清理动态分配的内存。 可以用用户定义的特性来标记类或方法。这可以用于文档说明，对编译有一定的影响(例如，把方法标记为只在调试时编译)。 对.NET基类库的完全访问权，并易于访问Windows API。 可以使用指针和直接内存访问，但C#语言可以在没有它们的条件下访问内存。 以VB的风格支持属性和事件。 改变编译器选项，可以把程序编译为可执行文件或.NET组件库，该组件库可以用与ActiveX控件(COM组件)相同的方式由其他代码调用。 C#可以用于编写ASP.NET动态Web页面和XML Web

28、服务。应该指出，对于上述大多数特性，VB.NET和Managed C+也具备。但C#从一开始就使用.NET，对.NET特性的支持不仅是完整的，而且提供了比其他语言更合适的语法。C#语言本身非常类似于Java，但其中有一些改进，因为Java并不是为应用于.NET环境而设计的。在结束这个主题前，还要指出C#的两个局限性。其一是该语言不适用于编写时间急迫或性能非常高的代码，例如一个要运行1000或1050次的循环，并在不需要这些循环时，立即清理它们所占用的资源。在这方面，C+可能仍是所有低级语言中的佼佼者。其二是C#缺乏性能极高的应用程序所需要的关键功能，包括保证在代码的特定地方运行的内联函数和析构

29、函数。但这类应用程序非常少。出处：Professional C#Third Edition作者：Simon RobinsonChristian NagelJay GlynnMorgan SkinnerKarli WatsonBill Evjen五分钟搞定5000字毕业论文外文翻译，你想要的工具都在这里!在科研过程中阅读翻译外文文献是一个非常重要的环节，许多领域高水平的文献都是外文文献，借鉴一些外文文献翻译的经验是非常必要的。由于特殊原因我翻译外文文献的机会比较多，慢慢地就发现了外文文献翻译过程中的三大利器：Google“翻译”频道、金山词霸（完整版本）和CNKI“翻译助手。具体操作过程如下：

30、1.先打开金山词霸自动取词功能，然后阅读文献； 2.遇到无法理解的长句时，可以交给Google处理，处理后的结果猛一看，不堪入目，可是经过大脑的再处理后句子的意思基本就明了了； 3.如果通过Google仍然无法理解，感觉就是不同，那肯定是对其中某个“常用单词”理解有误，因为某些单词看似很简单，但是在文献中有特殊的意思，这时就可以通过CNKI的“翻译助手”来查询相关单词的意思，由于CNKI的单词意思都是来源与大量的文献，所以它的吻合率很高。 另外，在翻译过程中最好以“段落”或者“长句”作为翻译的基本单位，这样才不会造成“只见树木，不见森林”的误导。四大工具： 1、Google翻译： google

31、，众所周知，谷歌里面的英文文献和资料还算是比较详实的。我利用它是这样的。一方面可以用它查询英文论文，当然这方面的帖子很多，大家可以搜索，在此不赘述。回到我自己说的翻译上来。下面给大家举个例子来说明如何用吧比如说“电磁感应透明效应”这个词汇你不知道他怎么翻译，首先你可以在CNKI里查中文的，根据它们的关键词中英文对照来做，一般比较准确。 在此主要是说在google里怎么知道这个翻译意思。大家应该都有词典吧，按中国人的办法，把一个一个词分着查出来，敲到google里，你的这种翻译一般不太准，当然你需要验证是否准确了，这下看着吧，把你的那支离破碎的翻译在google里搜索，你能看到许多相关的文献或资

32、料，大家都不是笨蛋，看看，也就能找到最精确的翻译了，纯西式的！我就是这么用的。 2、CNKI翻译： CNKI翻译助手，这个网站不需要介绍太多，可能有些人也知道的。主要说说它的有点，你进去看看就能发现：搜索的肯定是专业词汇，而且它翻译结果下面有文章与之对应（因为它是CNKI检索提供的，它的翻译是从文献里抽出来的），很实用的一个网站。估计别的写文章的人不是傻子吧，它们的东西我们可以直接拿来用，当然省事了。网址告诉大家，有兴趣的进去看看，你们就会发现其乐无穷！还是很值得用的。 3、网路版金山词霸（不到1M）： 4、有道在线翻译：翻译时的速度：这里我谈的是电子版和打印版的翻译速度，按个人翻译速度看，打

33、印版的快些，因为看电子版本一是费眼睛，二是如果我们用电脑，可能还经常时不时玩点游戏，或者整点别的，导致最终SPPEED变慢，再之电脑上一些词典（金山词霸等）在专业翻译方面也不是特别好，所以翻译效果不佳。在此本人建议大家购买清华大学编写的好像是国防工业出版社的那本英汉科学技术词典，基本上挺好用。再加上网站如：google CNKI翻译助手，这样我们的翻译速度会提高不少。具体翻译时的一些技巧（主要是写论文和看论文方面） 大家大概都应预先清楚明白自己专业方向的国内牛人，在这里我强烈建议大家仔细看完这些头上长角的人物的中英文文章，这对你在专业方向的英文和中文互译水平提高有很大帮助。 我们大家最蹩脚的实

34、质上是写英文论文，而非看英文论文，但话说回来我们最终提高还是要从下大工夫看英文论文开始。提到会看，我想它是有窍门的，个人总结如下： 1、把不同方面的论文分夹存放，在看论文时，对论文必须做到看完后完全明白（你重视的论文）；懂得其某部分讲了什么（你需要参考的部分论文），在看明白这些论文的情况下，我们大家还得紧接着做的工作就是把论文中你觉得非常巧妙的表达写下来，或者是你论文或许能用到的表达摘记成本。这个本将是你以后的财富。你写论文时再也不会为了一些表达不符合西方表达模式而烦恼。你的论文也降低了被SCI或大牛刊物退稿的几率。不信，你可以试一试 2、把摘记的内容自己编写成检索，这个过程是我们对文章再回顾，而且是对你摘抄的经典妙笔进行梳理的重要阶段。你有了这个过程。写英文论文时，将会有一种信手拈来的感觉。许多文笔我们不需要自己再翻译了。当然前提是你梳理的非常细，而且中英文对照写的比较详细。 3、最后一点就是我们往大成修炼的阶段了，万事不是说成的，它是做出来的。写英文论文也就像我们小学时开始学写作文一样，你不练笔是肯定写不出好作品来的。所以在此我鼓励大家有时尝试着把自己的论文强迫自己写成英文的，一遍不行，可以再修改。最起码到最后你会很满意。呵呵，我想我是这么觉得的。