To Clone or Not To Clone?

[Brian Keating]

Hi there,
Consider this from MSDN
*Notes to Inheritors When you derive from DataGridViewChe ckBoxCell and add
new properties to the derived class, be sure to override the Clone method to
copy the new properties during cloning operations. You should also call the
base class's Clone method so that the properties of the base class are copied
to the new cell. *

How should I do this?
a)
public override object Clone()
{
MemberwiseClone ();
}
// this is no good jsut a shallow copy
b)
public override object Clone()
{
NumericDataGrid ViewTextBox tb = (NumericDataGri dViewTextBox)ba se.Clone();
tb.MaxValue = this.MaxValue;
tb.MinValue = this.MinValue;
return tb;
}

// This seems to work; but is it? I.e. the base.Clone is only returning a
base object so surely when i cast to a derived object and start writing my
max min integers i over write some of the base somehow?

....tnx in advance, brian

[Bruce Wood]

It really depends upon how smart the base class's Clone is. If it
simply instantiates a base object, then your cast will fail when you
try to assign it to "tb". If the base class's Clone method is clever
and uses reflection to decide what to instantiate, it may work.

As an aside, this is why I implement Clone within my own classes as
Clone plus CopyTo: then I override like this:

public override DerivedClass Clone()
{
DerivedClass obj = new DerivedClass();
this.CopyTo(obj );
return obj;
}

protected override void CopyTo(BaseClas s other)
{
base.CopyTo(oth er);
DerivedClass otherDerived = (DerivedClass)o ther;
otherDerived._f ield1 = this._field1;
... etc ...
}

However, if you don't have control over the base class, then you can't
do this.

[Brian Keating]

Hi Bruce,

Yip i though that this was the way to go myself but then i did a test
probram where my base class didn't use reflection for clone.
Results were amazing in that this works!

public override object Clone() // derived clone method
{
DerivedTextBox tb = (DerivedTextBox )base.Clone();
tb.MaxValue = this.MaxValue;
tb.MinValue = this.MinValue;
return tb;
}

basically it appears that if implemented this way things it works.
However if i tried to do that outside the class. i.e.
void Main()
{
BaseTextBox tbb = new BaseTextBox();
DerivedTextBox tbd = (DerivedTextBox )tbb.Clone(); // exception thrown

}
So I'm thinking i need to trawl through the language spec or the CLR spec to
find where they say that this is how using base clone works.

Thanks
Brian

"Bruce Wood" wrote:

It really depends upon how smart the base class's Clone is. If it
simply instantiates a base object, then your cast will fail when you
try to assign it to "tb". If the base class's Clone method is clever
and uses reflection to decide what to instantiate, it may work.

As an aside, this is why I implement Clone within my own classes as
Clone plus CopyTo: then I override like this:

public override DerivedClass Clone()
{
DerivedClass obj = new DerivedClass();
this.CopyTo(obj );
return obj;
}

protected override void CopyTo(BaseClas s other)
{
base.CopyTo(oth er);
DerivedClass otherDerived = (DerivedClass)o ther;
otherDerived._f ield1 = this._field1;
... etc ...
}

However, if you don't have control over the base class, then you can't
do this.

[Jon Skeet [C# MVP]]

Brian Keating wrote:

Yip i though that this was the way to go myself but then i did a test
probram where my base class didn't use reflection for clone.
Results were amazing in that this works!

The docs for MemberwiseClone aren't as good as they could be, but the
important bit is:

<quote>
The Type of the clone is the same as the type of the original Object.
</quote>

In other words, it doesn't matter what "level" you call it from, the
type of the cloned object is the same as the type of object you called
it on. So if BaseTextBox.Clo ne() calls MemberwiseClone () when the
instance is actually a DerivedTextBox, you still get a DerivedTextBox
returned.

Jon

[Brian Keating]

Thanks Jon,
Saved the day again.
Needed to know was this standard behaviour or was i by some fluke getting
the same results.

Thanks agian.
regds
Brian

"Jon Skeet [C# MVP]" wrote:

Brian Keating wrote:

Yip i though that this was the way to go myself but then i did a test
probram where my base class didn't use reflection for clone.
Results were amazing in that this works!

The docs for MemberwiseClone aren't as good as they could be, but the
important bit is:

<quote>
The Type of the clone is the same as the type of the original Object.
</quote>

In other words, it doesn't matter what "level" you call it from, the
type of the cloned object is the same as the type of object you called
it on. So if BaseTextBox.Clo ne() calls MemberwiseClone () when the
instance is actually a DerivedTextBox, you still get a DerivedTextBox
returned.

Jon