The 12th chapter of Java Programming thought

The previous time has been through the network Tutorial Learning Java Foundation, the object-oriented part of the study after the intention to continue to further study, but the feeling of haste, the foundation is not solid enough, so began a "Java programming thought", I hope that the foundation to play well, and then in-depth study.

I have to say that this book is really not the wave of fame, for a novice like me after reading one or two chapters also feel that this book is worth buying. Unlike on-line tutorials, this book begins with a thorough discussion of the understanding of objects in Java object-oriented programming, and it's worth noting that if you don't have the basics of Java programming before, the first chapter looks like a lot of effort, and the effect is not very good, because it's not the theory that uses code to illustrate, So the author also supports starting with the following code, and then comes back to the first chapter.

The first chapter I see from the beginning of the inheritance interface those, obviously deepened the understanding of Java syntax, but then the look is a little hard, but also because the code has not been learned directly to see some boring theory, so from here to jump to the second chapter, first understand and come back to deepen learning.

The title of the second chapter is very interesting--everything is an object, there is a deeper understanding of "object" and "object reference", so that it is mainly because it has not been clear what the object reference refers to. objects can only be created by new, and the identifier we manipulate (that is, the name of the object) is actually a reference to the object, the object's reference to the object's address, not the object. Then the second chapter also commented on the comments and embedded documents, feel this put in the first chapter a little early, so first skipped.

"Java programming thought" good use of words believe that can learn a lot of things, but there is a dislike of the place is that most of his practice is to download the code provided by the author to do, and then I do not want to toss this, so the practice also need to strengthen.

The 12th chapter of Java Programming thought