Java tutorial part 4
Download as PPTX, PDF•2 likes•571 views
The document discusses key concepts related to Java object methods, including the clone() method and its requirements for functioning correctly in subclasses. It explains the differences between shallow and deep copies when cloning objects, as well as the importance of overriding methods like toString(), equals(), and hashCode() for meaningful object comparisons and representations. Additionally, it touches on the finalize() method and its role in resource management during garbage collection.
Java tutorial part 4
- 1. The Object Class • Every java class has Object as its superclass and thus inherits the Object methods. • Object is a non-abstract class • Many Object methods, however, have implementations that aren’t particularly useful in general • In most cases it is a good idea to override these methods with more useful versions. • In other cases it is required if you want your objects to correctly work with other class libraries.
- 2. Clone Method • Recall that the “=“ operator simply copies Object references. e.g., >> Student s1 = new Student(“Smith”, Jim, 3.13); >> Student s2 = s1; >> s1.setName(“Sahil”); >> System.out.println(s2.getName()); OP:- Sahil • What if we want to actually make a copy of an Object? • Most elegant way is to use the clone() method inherited from Object. Student s2 = (Student) s1.clone();
- 3. About clone() method • First, note that the clone method is protected in the Object class. • This means that it is protected for subclasses as well. • Hence, it cannot be called from within an Object of another class and package. • To use the clone method, you must override in your subclass and upgrade visibility to public. • Also, any class that uses clone must implement the Cloneable interface. • This is a bit different from other interfaces that we’ve seen. • There are no methods; rather, it is used just as a marker of your intent. • The method that needs to be implemented is inherited from Object.
- 4. Issue With clone() method • Finally, clone throws a CloneNotSupportedException. • This is thrown if your class is not marked Cloneable. • This is all a little odd but you must handle this in subclass.
- 5. Steps For Cloning • To reiterate, if you would like objects of class C to support cloning, do the following: – implement the Cloneable interface – override the clone method with public access privileges – call super.clone() – Handle CloneNotSupported Exception. • This will get you default cloning means shallow copy.
- 6. Shallow Copies With Cloning • We haven’t yet said what the default clone() method does. • By default, clone makes a shallow copy of all iv’s in a class. • Shallow copy means that all native datatype iv’s are copied in regular way, but iv’s that are objects are not recursed upon – that is, references are copied. • This is not what you typically want. • Must override clone explicitly for Deep Copying.
- 7. Deep Copies • For deep copies that recurse through the object iv’s, you have to do some more work. • super.clone() is first called to clone the first level of iv’s. • Returned cloned object’s object fields are then accessed one by one and clone method is called for each. • See DeepClone.java example
- 8. Additional clone() properties • Note that the following are typical, but not strictly required: – x.clone() != x; – x.clone().getClass() == x.getClass(); – x.clone().equals(x); • Finally, though no one really cares, Object does not support clone();
- 9. toString() method • The Object method String toString(); is intended to return a readable textual representation of the object upon which it is called. This is great for debugging! • Best way to think of this is using a print statement. If we execute: System.out.println(someObject); we would like to see some meaningful info about someObject, such as values of iv’s, etc.
- 10. default toString() • By default toString() prints total garbage that no one is interested in getClass().getName() + '@' + Integer.toHexString(hashCode()) • By convention, print simple formatted list of field names and values (or some important subset). • The intent is not to overformat. • Typically used for debugging. • Always override toString()!
- 11. equals() method • Recall that boolean == method compares when applied to object compares references. • That is, two object are the same if the point to the same memory. • Since java does not support operator overloading, you cannot change this operator. • However, the equals method of the Object class gives you a chance to more meaningful compare objects of a given class.
- 12. equals method, cont • By default, equals(Object o) does exactly what the == operator does – compare object references. • To override, simply override method with version that does more meaningful test, ie compares iv’s and returns true if equal, false otherwise. • See Equals.java example in course notes.
- 13. equals subtleties • As with any method that you override, to do so properly you must obey contracts that go beyond interface matching. • With equals, the extra conditions that must be met are discussed on the next slide:
- 14. equals contract It is reflexive: for any reference value x, x.equals(x) should return true. It is symmetric: for any reference values x and y, x.equals(y) should return true if and only if y.equals(x) returns true. It is transitive: for any reference values x, y, and z, if x.equals(y) returns true and y.equals(z) returns true, then x.equals(z) should return true. It is consistent: for any reference values x and y, multiple invocations of x.equals(y) consistently return true or consistently return false, provided no information used in equals comparisons on the object is modified. For any non-null reference value x, x.equals(null) should return false.
- 15. hashcode() method • Java provides all objects with the ability to generate a hash code. • By default, the hashing algorithm is typically based on an integer representation of the java address. • This method is supported for use with java.util.Hashtable • Will discuss Hashtable in detail during Collections discussion.
- 16. Rules for overriding hashcode • Whenever invoked on the same object more than once, the hashCode method must return the same integer, provided no information used in equals comparisons on the object is modified. • If two objects are equal according to the equals(Object) method, then calling the hashCode method on each of the two objects must produce the same integer result. • It is not required that if two objects are unequal according to the equals(java.lang.Object) method, then calling the hashCode method on each of the two objects must produce distinct integer results. However, the programmer should be aware that producing distinct integer results for unequal objects may improve the performance of hashtables.
- 17. finalize() method • Called as final step when Object is no longer used, just before garbage collection • Object version does nothing • Since java has automatic garbage collection, finalize() does not need to be overridden reclaim memory. • Can be used to reclaim other resources – close streams, database connections, threads. • However, it is strongly recommended not to rely on this for scarce resources. • Be explicit and create own dispose method.