Poornachandra Sarang

author
+ Follow
since Apr 17, 2012
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
5
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Poornachandra Sarang

Constructor "initializes" the state of the object and is not used for "creating" the object as the name deceptively suggests. When JVM loads a class, its entire definition is injected into the memory. When a draw() method is called in the superclass constructor, the runtime looks up the polymorphic definition of the draw() method and finds that there is an overridden draw() method available and thus calls the subclass (RoundGlyph) draw() implementation. Try commenting the draw() method in the subclass and the runtime would call the superclass implementation. The point to note that the entire class definition is always available in memory and calling an object method has no connection to whether the object is fully initialized or not.
8 years ago
Chapter 21 covers String class, Date and time classes, and Introspection & Reflection. Each section has elaborate coding examples.
8 years ago
With the great penetration of mobiles in the worlds, the flat-client applications for mobile devices are on rise again. There is no reason to ignore Swing development completely.
8 years ago
The book's focus in on the entire Java language. Just skip the material on Java 7 (if you desire so) which has been clearly marked.
8 years ago
Here is a quote from my book (pp 81):

"... This feature is called compile time polymorphism. The compiler resolves which implementation to call at the compile time, thus the name. We also have a feature known as runtime polymorphism whereby the Java runtime decides during the program execution which implementation to call."

As I have been claiming in the book and the posts in this forum, that the main focus was to bring in absolute (if not at least near absolute) technical accuracy in the book. So I have put in my best efforts in selecting the most accurate nomenclature throughout, coupled with rigorous technical reviews. I have seen the use of both terms "compile" and "runtime" in several literatures including Sun's official curriculum. I would like to add that in my earlier comment, I used the word "incomplete" which is more appropriate than calling it "conflicting".

I do not wish to start a debate on this and do respect the different opinions in the academics and the industry.
8 years ago
The book clearly distinguishes Java 7 features from the rest. While reading the book, you may comfortably skip sections on Java 7.
8 years ago
The book provides in-depth coverage of OOP concepts with several appropriate examples. If your question is targeted to "Object-oriented Analysis and Design", then the book does not cover OOAD.
8 years ago
The polymorphism can be either compile or runtime. So saying "at runtime" makes its definition incomplete.
8 years ago
The book expects you to be a programmer in any computer language. Please refer to my post in the thread "Another question about who the book is addressed to" in the current forum for more details.
8 years ago
Please refer to my post in the thread "Another question about who the book is addressed to" in the current forum.
8 years ago
The following is taken from http://docs.oracle.com/javase/7/docs/technotes/guides/collections/changes7.html

Collections Framework Enhancements in Java SE 7
The interface TransferQueue has been added. It is a refinement of the BlockingQueue interface in which producers can wait for consumers to receive elements. One implementation of the new interface is also included in this release, LinkedTransferQueue.

The book provides a detailed discussion on this addition and a dedicated example on the use of LinedTranferQueue.
8 years ago
Please refer to my post in the thread "Another question about who the book is addressed to" in the current forum.
8 years ago
There are about 15 pages in the last chapter that describe "Introspection and Reflection" with a detailed example. As RMI is a server side programming, this book does not cover it. Refer to http://docs.oracle.com/javase/tutorial/rmi/index.html.
8 years ago
I have dedicated three chapters on threads with carefully chosen examples. Thanks to Danny (Chief Architect Java SE7) who made me rewrite all the examples from my first submission to bring in more practical and in-context examples. I agree with Rob - if you want an ultimate, authentic, in-depth information on threading "Java Concurrency in Practice" is the book to refer to - you would need lots of patience and concentration while reading it.
8 years ago
Bill, if you read the "Acknowledgments" in the book, you would understand the real motivation behind writing this book. I have trained and accessed several trainers of the Sun Authorized Training Centers since 1996 and thus have been in constant touch with Core Java. During the delivery of SL275 and several other courses from Sun's curriculum, I realized that there were many errors in the material available to these aspiring candidates. The early versions of the official curriculum too had a few technical errors. So I always wanted to bring out the material which would be technical accurate. I feel that I achieved it with the support from Oracle team - just to mention two important names, John Pampuch, Director Java VM technology and Danny Coward, Chief Architect Java SE 7 who provided a technical review of the manuscript "twice". As I said, I am satisfied with the contents accuracy. However, there may be a few errors, specifically typos which may have gone unnoticed. I request the readers to bring such errors, if any, to my notice and we will publish the errata on the book's site.

The book is for professional programmers who want an authentic and accurate information on Language syntax and core libraries. As I mentioned in my another post, it can also be used as a classroom text. It is definitely not a begineer's tutorial on Java.
8 years ago