Thinking in Java (One-Off) [Englisch] [Taschenbuch]

Dieser Titel ist in englischer Sprache.
Thinking in Java ist die gedruckte Version von Bruce Eckels Online-Materialien und behandelt Java speziell für diejenigen, die bereits Programmierkenntnisse haben. Die Einführung des Autors in das Wesen von Java als neue Programmiersprache und die gründliche Erläuterung der Merkmale von Java machen dieses Buch zu einem brauchbaren Handbuch.

Thinking in Java beginnt ein wenig esoterisch mit den Überlegungen des Autors, was an Java neu und besser ist. (Der Schrifttyp für die Kapitelüberschriften in diesem Buch ist außergewöhnlich anstrengend für die Augen.) Er legt kurz und deutlich dar, wie man mit Java auf einfache Weise seine Programmierfähigkeiten erweitern und verbessern kann. Wirklich gut an dem Buch sind dann die Erklärungen zu den Merkmalen der Programmiersprache. Es gibt eine Anleitung zu den Java-Basistypen, Schlüsselworten und Operatoren. Das Handbuch schließt ausführliche Quellcodes ein, die manchmal etwas entmutigen (wie es beim Beispielcode für alle Java-Operatoren in einem Listing der Fall ist). Kurz, das Buch erweist sich für erfahrene Entwickler als sehr nützlich.

Es geht weiter mit Problemen des Klassendesign, wann man Vererbung und Komposition verwendet, und mit Themen im Zusammenhang mit Kapselung und Polymorphie. (Die Erläuterungen zu den Inner-Klassen und Geltungsbereichen werden den meisten Lesern ein bißchen übertrieben erscheinen.) Das Kapitel zu den Java-Sammelklassen sowohl für das Java Developer's Kit (JDK) 1.1 als auch für die neuen Klassen, wie Sätze, Listen und Maps, ist weit besser. Das Material aus diesem Kapitel werden Sie sonst wahrscheinlich nirgendwo finden.

Kapitel über Ausnahmebehandlung und Programmieren mit Typinformation sind ebenso von Nutzen wie die Kapitel zu den neuen Swing-Interface-Klassen und zur Netzwerkprogrammierung. Obwohl das Buch eher eine bunte Mischung anbietet, enthält Thinking in Java hervorragendes Material für objektorientiert arbeitenden Programmierer, die wissen möchten, was es mit Java auf sich hat.

Thinking in Java ist von den Grundlagen der Javasyntax bis hin zu den fortgeschritteneren Merkmalen (Netzwerkprogrammierung, fortgeschrittene objektorientierte Fähigkeiten, Multithreading) darauf ausgerichtet, Java zu lehren und zu vermitteln. Bruce Eckels gut lesbarer Stil und die kleinen, direkten Programmierbeispiele verdeutlichen sogar die kompliziertesten Konzepte. -- Dieser Text bezieht sich auf eine vergriffene oder nicht verfügbare Ausgabe dieses Titels.

Programming languages have similarities with general purpose languages such as Spanish. You might know enough Spanish to cobble together a simple letter or read a poster but the real breakthrough comes when you can think in it. Thinking in Java attempts to improve your understanding to the point where you can think about a programming problem in Java rather than in English or whatever and then translate it. This fits extremely well with the basic Java ethos, which is to enable you to frame a problem in terms of the Java objects you'll use to provide a solution.

Eckel approaches teaching you to think in Java by introducing a topic, talking around it to put it in context, providing examples to try and then discussing them in depth. Each chapter has a summary followed by exercises. The book is structured for someone coming from a procedural language background. Eckel spends a lot of time on OOP concepts in general and the way in which it's implemented in Java. After covering operators Eckel goes on to program flow, initialisation and garbage collection, packages, class reuse, polymorphism and so on all the way up to distributed programming (servlets) and appendices on passing objects, the JNI, guidelines and resources. The whole book is also on CD (in several formats including HTML) with the source code (guaranteed to compile under Linux using Java 1.2.2). The CD also contains Thinking in C: Foundations for C++and Java.

Thinking In Java is basically a tutorial. You're intended to read it linearly and work the exercises. It helps that it's well written but it helps even more to have a programming background. If not, you'll probably want a straight Java reference to hand as well. --Steve Patient -- Dieser Text bezieht sich auf eine vergriffene oder nicht verfügbare Ausgabe dieses Titels.

Perfect for migrating to Java from a fellow object-oriented language (such as C++), the second edition of Thinking in Java continues the earlier version's thoughtful approach to learning Java inside and out, while also bringing it up to speed with some of the latest in Java 2 features. This massive tutorial covers many of the nooks and crannies of the language, which is of great value in the programming world.

The most prominent feature of the book is its diligent and extremely thorough treatment of the Java language, with special attention to object design. (For instance, 10 pages of sample code show all of the available operators.) Some of the best thinking about objects is in this book, including when to use composition over inheritance. The esoteric details of Java in regard to defining classes are thoroughly laid out. (The material on interfaces, inner classes, and designing for reuse will please any expert.) Each section also has sample exercises that let you try out and expand your Java knowledge.

Besides getting the reader to "think in objects," Thinking in Java also covers other APIs in Java 2. Excellent sections include an in-depth tour of Java's collection and stream classes, and enterprise-level APIs like servlets, JSPs, EJBs, and RMI. Weighing in at over 1,000 pages, any reader who is serious about learning Java inside and out will want to take a look at this superior resource on some of the latest and most advanced thinking in object design. --Richard Dragan

Topics covered:

Object-design basics Inheritance and polymorphism Object lifetimes Exception handling Multithreading and persistence Java on the Internet Analysis and design basics Java basics: keywords and flow control Initializing objects Garbage collection Java packages Designing for reuse: composition vs. inheritance The final keyword Interfaces and inner classes Arrays and container classes

Java I/O classes Run-time type identification UI design basics with Swing Deploying to JAR files Network programming with sockets JDBC database programming Introduction to servlets JavaServer Pages (JSPs) RMI CORBA Enterprise JavaBeans (EJBs) and Jini Cloning objects The Java Native Interface (JNI) Java programming guidelines

-- Dieser Text bezieht sich auf eine vergriffene oder nicht verfügbare Ausgabe dieses Titels.

Revised and updated third edition.

Thinking in Java, Third Edition is the much-anticipated revision of Bruce Eckel's best-selling introduction to Java. In Thinking in Java, 3/e, Bruce Eckel provides complete integration of JDK 1.4 technologies to his award winning 'Thinking in' presentation. Eckel introduces all the basics of objects as Java uses them, then walks carefully through the fundamental concepts underlying all Java programming -- including program flow, initialization and cleanup, implementation hiding, reusing classes, and polymorphism. Using extensive, to-the-point examples, he introduces exception handling, Java I/O, run-time type identification, and passing and returning objects. Eckel also provides an overview of the Key Technology of the Java2 Enterprise Edition platform (J2EE). Thinking in Java won the 1999 Software Development Magazine Productivity Award, and the Java Developer's Journal Editor's Choice Award for best book of 1998!

Bruce Eckel's Thinking in Java—

• JavaWorld Editor's Choice Award for Best Book, 2001
• JavaWorld Reader's Choice Award for Best Book, 2000
• Software Development Magazine Productivity Award, 1999
• Java Developer's Journal Editor's Choice Award for Best Book, 1998
• Software Development Magazine Jolt Product Excellence Award (for Thinking in C++), 1995

Thinking in Java has earned raves from programmers worldwide for its extraordinary clarity, careful organization, and small, direct programming examples. From the fundamentals of Java syntax to its most advanced features (in-depth object-oriented concepts, multithreading, automated project building, unit testing, and debugging), Thinking in Java is designed to teach, one simple step at a time.

• The classic Java Introduction, fully updated for Java 2 version 1.4, with new topics throughout!
• New testing framework validates each program and shows you the output.
• New chapter on unit testing, automated building, assertions, logging, debugging, and other ways to keep your programs in tune.
• Completely rewritten threading chapter gives you a solid grasp of the fundamentals.
• 350+ working Java programs, rewritten for this edition. 15,000+ lines of code.
• Companion web site includes all source code, annotated solution guide, essays and other resources.
• Includes entire Foundations for Java multimedia seminar on CD-ROM for Windows, Linux and Mac.
• For beginners and experts alike.
• Teaches Java linguistics, not platform-dependent mechanics.
• Thorough coverage of fundamentals; demonstrates advanced topics.
• Explains sound object-oriented principles as they apply to Java.
• Hands-on Java CD available online, with 15 hours of lectures and slides by Bruce Eckel.
• Live seminars, consulting, and reviews available.

www.BruceEckel.com

What people are saying—

"The best book on Java...Your depth is amazing." "Definitely the thinking person's choice in a Java book." "One of the absolutely best programming tutorials I've seen, for any language."

BRUCE ECKEL is president of Mindview, Inc., which provides public and private training seminars, consulting, mentoring, and design reviews in Object-Oriented technology and Design Patterns. He is the author of Thinking in C++, Volume 2, and other books, has written over 150 articles, and has given lectures and seminars throughout the world for over 20 years. He has served as a voting member of the C++ Standards Committee. He holds a BS in Applied Physics and an MS in Computer Engineering.

Preface

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 the computer 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 out 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 maintaining programs.1 Of course, many language design decisions were made with complexity in mind, but at some point there were always some other issues that were considered essential to be added into the mix. Inevitably, those other issues are what cause programmers to eventually "hit the wall" with that language. For example, C++ had to be backwards-compatible with C (to allow easy migration for C programmers), as well as efficient. Those are both very useful goals and account for much of the success of C++, but they also expose extra complexity that prevents some projects from being finished (certainly, you can blame programmers and management, but if a language can help by catching your mistakes, why shouldn't it?). As another example, Visual BASIC (VB) was tied to BASIC, which wasn't really designed to be an extensible language, so all the extensions piled upon VB have produced some truly horrible and unmaintainable syntax. Perl is backwards-compatible with Awk, Sed, Grep, and other Unix tools it was meant to replace, and as a result is often accused of producing "write-only code" (that is, after a few months you can't read it). On the other hand, C++, VB, Perl, and other languages like Smalltalk had some of their design efforts focused on the issue of complexity and as a result are remarkably successful in solving certain types of problems.

What has impressed me most as I have come to understand Java is that somewhere in the mix of Sun's design objectives, it appears that there was the goal of reducing complexity for the programmer. As if to say "we care about reducing the time and difficulty of producing robust code." In the early days, this goal resulted in code that didn't run very fast (although there have been many promises made about how quickly Java will someday run) but it has indeed produced amazing reductions in development time; half or less of the time that it takes to create an equivalent C++ program. This result alone can save incredible amounts of time and money, but Java doesn't stop there. It goes on to wrap many of the complex tasks that have become important, such as multithreading and network programming, in language features or libraries that can at times make those tasks easy. And finally, it tackles some really big complexity problems: cross-platform programs, dynamic code changes, and even security, each of which can fit on your complexity spectrum anywhere from "impediment" to "show-stopper." So despite the performance problems we've seen, the promise of Java is tremendous: it can make us significantly more productive programmers.

One of the places I see the greatest impact for this is on the Web. Network programming has always been hard, and Java makes it easy (and the Java language designers are working on making it even easier). Network programming is how we talk to each other more effectively and cheaper than we ever have with telephones (email alone has revolutionized many businesses). As we talk to each other more, amazing things begin to happen, possibly more amazing even than the promise of genetic engineering.

In all ways—creating the programs, working in teams to create the programs, building user interfaces so the programs can communicate with the user, running the programs on different types of machines, and easily writing programs that communicate across the Internet—Java increases the communication bandwidth between people. I think that the results of the communication revolution may not be seen from the effects of moving large quantities of bits around; we shall see the true revolution because we will all be able to talk to each other more easily: one-on-one, but also in groups and, as a planet. I've heard it suggested that the next revolution is the formation of a kind of global mind that results from enough people and enough interconnectedness. Java may or may not be the tool that foments that revolution, but at least...