CodeGuru Staff

Bruce Eckel’s Thinking in Java Contents | Prev | Next All the source code for this book is available as copyrighted freeware, distributed as a single package, by visiting the Web site http://www.BruceEckel.com. To make sure that you get the most current version, this is the official site for distribution of the code and the […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next Thinking in Java Bruce Eckel Comments from readers: Much better than any other Java book I’ve seen. Make that “by an order of magnitude”… very complete, with excellent right-to-the-point examples and intelligent, not dumbed-down, explanations … In contrast to many other Java books I found […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next You’ve seen in this chapter that the standard Java library has some fairly useful collections, but far from a complete set. In addition, algorithms like sorting are not supported at all. One of the strengths of C++ is its libraries, in particular the Standard Template […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next One of the things missing in the Java 1.0 and 1.1 libraries is algorithmic operations, even simple sorting. So it makes sense to create a Vector that sorts itself using the classic Quicksort. A problem with writing generic sorting code is that sorting must perform […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next The standard Java 1.0 and 1.1 library comes with a bare minimum set of collection classes, but they’re probably enough to get by with for many of your programming projects. (As you’ll see at the end of this chapter, Java 1.2 provides a radically redesigned […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next In any collection class, you must have a way to put things in and a way to get things out. After all, that’s the primary job of a collection – to hold things. In the Vector, addElement( ) is the way that you insert objects, and […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next To summarize what we’ve seen so far, your first, most efficient choice to hold a group of objects should be an array, and you’re forced into this choice if you want to hold a group of primitives. In the remainder of the chapter we’ll look […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next Most of the necessary introduction to arrays is in the last section of Chapter 4, which shows how you define and initialize an array. Holding objects is the focus of this chapter, and an array is just one way to hold objects. But there are […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next Once you learn about polymorphism, it can seem that everything ought to be inherited because polymorphism is such a clever tool. This can burden your designs; in fact if you choose inheritance first when you’re using an existing class to make a new class things […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next your objects It’s a fairly simple program that has only a fixed quantity of objects with known lifetimes. In general, your programs will always be creating new objects based on some criteria that will be known only at the time the program is running. You […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next In Java 1.1 it’s possible to place a class definition within another class definition. This is called an inner class . The inner class is a useful feature because it allows you to group classes that logically belong together and to control the visibility of […]

Bruce Eckel’s Thinking in Java Contents | Prev | Next The interface keyword takes the abstract concept one step further. You could think of it as a “pure” abstract class. It allows the creator to establish the form for a class: method names, argument lists and return types, but no method bodies. An interface can […]