I keep getting the same issue over and over again where an object I want to reference is copied or where an object I want to copy is referenced. This happens when I use the = operator.
For example, if I am sending the object to another form, ie:
SomeForm myForm = new SomeForm();
SomeObject myObject = new SomeObject();
myForm.formObject = myObject;
...and then modify the object in the form, the original object does not get modified. It is as if the object was copied and not referenced. Yet, when I do this:
SomeObject myObject = new SomeObject();
SomeObject anotherObject = new SomeObject();
anotherObject = myObject;
...and then modify anotherObject
, myObject
gets modified as well.
The most aggravating case is when I try to Clone one of my defined objects:
public class SomeObject
{
double value1, value2;
//default constructor here
public SomeObject(val1, val2)
{
value1 = val1;
value2 = val2;
}
public void Clone(SomeObject thingToCopy)
{
this.value1 = thingToCopy.value1;
this.value2 = thingToCopy.value2;
}
}
when I do this...
SomeObject obj1 = new SomeObject(1, 2);
SomeObject obj2 = new SomeObject();
obj2.Clone(obj1);
...obj1
is referenced and any modifications to obj2
changes obj1
.
System objects such as int, double, string
, etc seem to always be copied, except for in the case of the clone method above.
My question is, not taking into account the use of the ref
keyword in functions, when does an object get copied and when does an object get referenced in every case of the matter (i.e. when passing to functions, when setting as other objects (like the first two above examples), when copying member variables like the third example, etc.)?
It's hard to answer this sort of question precisely without spending an awful lot of time picking your words carefully.
I've done so in a couple of articles which you may find useful:
That's not to say that the articles are perfect, of course - far from it - but I've tried to be as clear as I can.
I think one important thing is to separate the two concepts (parameter passing and reference vs value types) out in your head.
To look at your specific examples:
SomeForm myForm = new SomeForm();
SomeObject myObject = new SomeObject();
myForm.formObject = myObject;
This means that myForm.formObject
and myObject
refer to the same instance of SomeObject
- like two people having separate pieces of paper, with each one having the same address written on them. If you go to the address on one piece of paper and paint the house red, then go to the address on the second piece of paper, you'll see a red house.
It's not clear what you mean by "and then modify the object in the form" because the type you have provided is immutable. There's no way of modifying the object itself. You can change myForm.formObject
to refer to a different instance of SomeObject
, but that's like scribbling out the address on one piece of paper and writing a different address on it instead. That won't change what's written on the other piece of paper.
If you could provide a short but complete program whose behaviour you don't understand (ideally a console application, just to keep things shorter and simpler) it would be easier to talk about things in concrete terms.