Java编程思想（英文版·第3版）附光盘 - (2010 年度畅销榜NO.120 )

本书经典的Java介绍，完全针对Java1.4版本更新，并增加了许多新主题。350多个可运行的Java程序，15000多行代码。讲述Java的同时着得阐释面向对象原理。支持网站包括所有源代码、带注释的解决方案指南、评论以及其他资源。随书光盘包括可用于Windows、Linux和Mac的完整的Fundations for Java多媒体研讨教材。本书的全面性，适用于初学者；本书的深入性，适用于专家。随书光盘含有15个小时的Bruce Eckel演讲课程。

Preface \r\nIntroduction\r\n1.Introduction to Objects\r\n2.Everything is an Object\r\n3.Controlling Program Flow\r\n4.Initialization & Cleanup\r\n5.Hiding the Implementation\r\n6.Reusing Classes\r\n7.Polymorphism\r\n8.Interfaces & Inner Classes\r\n9.Error Handling with Exceptions\r\n10.Detecting Types\r\n11.Collections of Objects\r\n12.The Java I/O System\r\n13.Concurrency\r\n14.Creating Windows & Applets\r\n15.Discovering Problems\r\n16.Analysis and Design\r\nA:Passing & Returning Objects\r\nB:Java Programming Guidelines\r\nC:Supplements\r\nD:Resources\r\nIndex

Bruce Eckel是MindView公司的总裁，他在面向对象技术和设计模式方面提供公开的和内部的培训研讨会、咨询、指导和设计评论。除本书外，Bruce Eckel还是《Thinking in C++》的作者，并与人合著了《Thinking in C#》、《Thinking in C++，Volume 2》。他发表过150多篇文章，有20多年世界各地的研讨会和演讲经验，他是C++标准委员会拥有表决权的成员之一，拥有应用物理学学士和计算机工程学硕士学位。

I suggested to my brother Todd, who is making the leap from hardware into programming, that the next big revolution will be in genetic engineering. We'll have microbes designed to make food, fuel, and plastic; they'll clean up pollution and in general allow us to master the manipulation of the physical world for a fraction of what it costs now. I claimed that it would make thecomputer revolution look small in comparison. Then I realized I was making a mistake common to science fiction writers: getting lost in the technology (which is of course easy to do in science fiction). An experienced writer knows that the story is never about the things; it's about the people. Genetics will have a very large impact on our lives, but I'm not so sure it will dwarf the computer revolution (which enables the genetic revolution)--or at least the information revolution. Information is about talking to each other: yes, cars and shoes and especially genetic cures are important, but in the end those are just trappings. What truly matters is how we relate to the world. And so much of that is about communication. This book is a case in point. A majority of folks thought I was very bold or a little crazy to put the entire thing up on the Web. "Why would anyone buy it?" they asked. If I had been of a more conservative nature I wouldn't have done it, but I really didn't want to write another computer book in the same old way. I didn't know what would happen but it turned out to be the smartest thing I've ever done with a book. For one thing, people started sending in corrections. This has been an amazing process, because folks have looked into every nook and cranny and caught both technical and grammatical errors, and I've been able to eliminate bugs of all sorts that I know would have otherwise slipped through. People have been simply terrific about this, very often saying "Now, I don't mean this in a critical way..." and then giving me a collection of errors I'm sure I never would have found. I feel like this has been a kind of group process and it has really made the book into something special. Because of the value of this feedback, I have created several incarnations of a system called "BackTalk" to collect and categorize comments. But then I started hearing "OK, fine, it's nice you've put up an electronic version, but I want a printed and bound copy from a real publisher." I tried very hard to make it easy for everyone to print it ont in a nice looking format but that didn't stem the demand for the published book. Most people don't want to read the entire book on screen, and hauling around a sheaf of papers, no matter how nicely printed, didn't appeal to them either. (Plus, I think it's not so cheap in terms of laser printer toner.) It seems that the computer revolution won't put publishers out of business, after all. However, one student suggested this may become a model for future publishing: books will be published on the Web first, and only if sufficient interest warrants it will the book be put on paper. Currently, the great majority of all books are financial failures, and perhaps this new approach could make the publishing industry more profitable. This book became an enlightening experience for me in another way. I originally approached Java as "just another programming language," which in many senses it is. But as time passed and I studied it more deeply, I began to see that the fundamental intention of this language was different from other languages I had seen up to that point. Programming is about managing complexity: the complexity of the problem you want to solve, laid upon the complexity of the machine in which it is solved. Because of this complexity, most of our programming projects fail. And yet, of all the programming languages of which I am aware, none of them have gone all-out and decided that their main design goal would be to conquer the complexity of developing and maintaini