@fcc: "Can anyone answer these?
Do you have to always have to call super.clone() in the clone() method you
write?
(For example, if your class wasn't extending anything (except Object, of
course)).
38.  If the base class is cloneable, what does the derived class have to do
to also be     cloneable?
39. To not be cloneable?
Class A implements Cloneable
A writes its own clone() method.
Class B extends A implements Cloneable
B doesn't write a clone() method.
Does a call to B go to A's clone(), or does it throw it an exception?
Thanks,
Mark"
    @jcbarda: "i'd imagine, if you wrote a final class, which was a direct subclass of 
object (i.e., no explicit super-class is defined for it), then clone 
wouldn't need to use super.clone(). in general, however, i don't see the 
harm of using it. especially when you might foresee a more developed 
class heirarchy after initial design.
as to your question, i haven't looked at the review, so this is just of 
the top of my head:
class B would have to explicitly implement Cloneable to avoid throwing 
an exception. think about classes that extend objecteven implicitly.
and if A writes a clone method, B would inherit it if its access is 
public. a call to o.clone, if o is a B, would call A's clone, and should 
be alright, since a B has everything an A would, and would only throw an 
exception if it didn't also explicitly implement Cloneable.
<quote>"
{'source': 'USENET', 'other_information': '{"reply_count": 1, "forum_name": "utexas.class.cs315.20150104.mbox"}', 'file': 'data/output/usenet-utexas.class.parquet'}