This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Question 26: Which of the following classes should have a custom finalize method? a. All class that creates socket b. All classes c. Any class that extends a class having a finalize method d. Any class that creates an array of primitive values Answer: a
I don't understand why a is correct? The finalize() method is unreliable so if it is implying that the class can close the socket from the finalize() method, then that is a wrong place to do it. I would say that the 'correct' answer should be c because finalize() may get executed, and the finalize() method inherited by the subclass may not work on the subclass. [ August 15, 2003: Message edited by: Alton Hernandez ]
You mistake the intent of having a finalize method - it should not be intended as the routine method for cleaning up but as the "last chance to fix things" in case of something odd happening. Thats why you will find finalize used in the standard Java library in places like java.io.FileInputStream. That way if you are sloppy at closing your FileInputStream - the finalize method may be able to keep you from running out of file handles. Having the full source to the standard libraries is a great resource for those studying the language. "Use the Source" Bill