大学英语六级158及答案解析.doc
《大学英语六级158及答案解析.doc》由会员分享,可在线阅读,更多相关《大学英语六级158及答案解析.doc(27页珍藏版)》请在麦多课文档分享上搜索。
1、大学英语六级 158及答案解析(总分:428.03,做题时间:132 分钟)一、Part I Writing (3(总题数:1,分数:30.00)1.For this part, you are allowed 30 minutes to write a short essay entitled Technology, a Blessing or a Curse? You should write at least 150 words following the outline given below: 1科学技术使人们的生活变得更加便利 2科学技术造成的负面影响 3我们应该怎样面对这种矛盾
2、(分数:30.00)_二、Part II Reading C(总题数:1,分数:71.00)Programming languages Programming languages are how people talk to computers. The computer would be just as happy speaking any language that was unambiguous. The reason we have high level languages is because people cant deal with machine language. The p
3、oint of programming languages is to prevent our poor frail human brains from being overwhelmed by a mass of detail. Architects know that some kinds of design problems are more personal than others. One of the cleanest, most abstract design problems is designing bridges. There your job is largely a m
4、atter of spanning a given distance with the least material. The other end of the spectrum is designing chairs. Chair designers have to spend their time thinking about human bodies. Software varies in the same way. Designing algorithms (运算法则) for routing data through a network is a nice, abstract pro
5、blem, like designing bridges. Whereas designing programming languages is like designing chairs: its all about dealing with human weaknesses. Most of us hate to acknowledge this. Designing systems of great mathematical elegance sounds a lot more appealing to most of us than pandering to human weaknes
6、ses. And there is a role for mathematical elegance: some kinds of elegance make programs easier to understand. But elegance is not an end in itself. And when I say languages have to be designed to suit human weaknesses, I dont mean that languages have to be designed for bad programmers. In fact I th
7、ink you ought to design for the best programmers, but even the best programmers have limitations. I dont think anyone would like programming in a language where all the variables were the letter x with integer subscripts. If you look at the history of programming languages, a lot of the best ones we
8、re languages designed for their own authors to use, and a lot of the worst ones were designed for other people to use. When languages are designed for other people, its always a specific group of other people: people not as smart as the language designer. So you get a language that talks down to you
9、. Cobol (计算机通用语言) is the most extreme case, but a lot of languages are pervaded by this spirit. It has nothing to do with how abstract the language is. C is pretty low-level, but it was designed for its authors to use, and thats why hackers like it. The argument for designing languages for bad progr
10、ammers is that there are more bad programmers than good programmers. That may be so. But those few good programmers write a disproportionately large percentage of the software. Im interested in the question, how do you design a language that the very best hackers will like? I happen to think this is
11、 identical to the question, how do you design a good programming language? Give the Programmer as Much Control as Possible. Many languages (especially the ones designed for other people) have the attitude of a governess: they try to prevent you from doing things that they think arent good for you. I
12、 like the opposite approach: give the programmer as much control as you can. When I first learned Lisp (表处理语言), what I liked most about it was that it considered me an equal partner. In the other languages I had learned up till then, there was the language and there was my program, written in the la
13、nguage, and the two were very separate. But in Lisp the functions and macros I wrote were just like those that made up the language itself. I could rewrite the language if I wanted. It had the same appeal as open-source software. Aim for Brevity. Brevity is underestimated and even scorned. But if yo
14、u look into the hearts of hackers, youll see that they really love it. How many times have you heard hackers speak fondly of how in, say, APL, they could do amazing things with just a couple lines of code? I think anything that really smart people really love is worth paying attention to. I think al
15、most anything you can do to make programs shorter is good. There should be lots of library functions; anything that can be implicit should be; the syntax (句法) should be simple; even the names of things should be short. And its not only programs that should be short. The manual should be thin as well
16、. A good part of manuals (说明书) is taken up with clarifications and reservations and warnings and special cases. If you force yourself to shorten the manual, in the best case you do it by fixing the things in the language that required so much explanation. Admit What Hacking Is. A lot of people wish
17、that hacking was mathematics, or at least something like a natural science. I think hacking is more like architecture. Architecture is related to physics, in the sense that architects have to design buildings that dont fall down, but the actual goal of architects is to make great buildings, not to m
18、ake discoveries about statistics. What hackers like to do is make great programs. And I think, at least in our own minds, we have to remember that its an admirable thing to write great programs, even when this work doesnt translate easily into the conventional intellectual currency of research paper
19、s. Intellectually, it is just as worthwhile to design a language programmers will love as it is to design a horrible one that embodies some idea you can publish a paper about. How to Organize Big Libraries? Libraries are becoming an increasingly important component of programming languages. Theyre a
20、lso getting bigger, and this can be dangerous. If it takes longer to find the library function that will do what you want than it would take to write it yourself, then all that code is doing nothing but make your manual thick. So I think we will have to work on ways to organize libraries. The ideal
21、would be to design them so that the programmer could guess what library call would do the right thing. Are People Really Scared of Prefix Syntax? This is an open problem in the sense that I have wondered about it for years and still dont know the answer. Prefix syntax seems perfectly natural to me,
22、except possibly for math. But it could be that a lot of Lisps unpopularity is simply due to having an unfamiliar syntax. Whether to do anything about it, if it is true, is another question. What Do You Need for Server (服务器)-Based Software? I think a lot of the most exciting new applications that get
23、 written in the next twenty years will be Web-based applications, meaning programs that sit on the server and talk to you through a Web browser. And to write these kinds of programs we may need some new things. One thing well need is support for the new way that server-based applications get release
- 1.请仔细阅读文档,确保文档完整性,对于不预览、不比对内容而直接下载带来的问题本站不予受理。
- 2.下载的文档,不会出现我们的网址水印。
- 3、该文档所得收入(下载+内容+预览)归上传者、原创作者;如果您是本文档原作者,请点此认领!既往收益都归您。
下载文档到电脑,查找使用更方便
2000 积分 0人已下载
下载 | 加入VIP,交流精品资源 |
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- 大学 英语六级 158 答案 解析 DOC
