You can then use it like this:

Rabbit r1 = new Rabbit();
Rabbit r2 = (Rabbit)r1.clone();

Instead of using super.clone(), you could use new Rabbit() and copy the fields one by one to the new object and return the new object. Then you don’t have to mess with CloneNotSupportedException.

If you were happy with a protected clone, that just blindly copied the raw bits of the object, you need not redefine your own version. Usually though, you would want a public one. Note you can’t create a private or default scope clone. You can only increase the visibility when you override.

The default protected clone does a shallow copy, that is, it does not make copies of objects pointed to by the object, but it copies all fields and references in an object. If you write your own clone, you might implement a deep copy, that is, also make copies of objects pointed to, and also objects pointed to by those objects recursively. Be careful. It is easy to create a chain reaction explosion or even an endless loop with a deep copy. Clone returns an Object not the type of the thing cloned. You need to cast it back.

If you are an assembler programmer you can think of clone as implemented by a native method that allocates a block of ram the same size as the existing object, then does a byte block move to copy the object literally byte for byte, then returns a handle to that new ram. I would like to see a variant of this sort of fast object construction for copy constructors. e.g. constructors of the form:

Clever Clone

Cloning Arrays

Learning More