c# = operator problem

Question

In C#, I have a simple 3D vector class.

static void Main(string[] args)
{
    Vector3D a, b;
    a = new Vector3D(0, 5, 10);
    b = new Vector3D(0, 0, 0);

    b = a;
    a.x = 10;

    Console.WriteLine("vector a=" + a.ToString());
    Console.WriteLine("vector b=" + b.ToString());
    Console.ReadKey();
}

the output is,

vector a= 10, 5, 10

vector b= 10, 5, 10

I assign a before i change a.x to 10. So i was expecting

vector a= 10, 5, 10

vector b= 0, 5, 10

From what i understand = operator assigns a reference to object like a pointer? And in C# i cant overload = operator.

Do i have to manually assign each property?

Answer 1

Yes, because Vecor3D is a class this is quite correct.

Classes are reference types and your b = a; statement does not copy a Vector3D instance but a reference to an instance.

If you want to 'clone' the instances, you could add the IClonable interface, but that is more or less abandoned.

A better solution for an <X,Y,Z> type might be to make it a struct. Structs are values types and the meaning of b = a; would change (towards what you want).

A 3D point meets all the criteria for a struct (small, no identity). The preferred way is to design it as immutable.

Answer 2

Yes, "= operator assigns a reference to object like a pointer", as you put it. Thus, both a and b reference the same single object in memory. (The object previously referenced by b is not referenced any more and will be garbage collected.)

There are multiple ways to overcome this problem:

1. Make Vector3D a struct instead of a class. Structs are value types instead of reference types, so b = a copies the contents of a to variable b.

2. Implement a Clone method in your Vector3D class (previously, this would mean implementing ICloneable, but this is no longer recommended). Alternatively, you could create a Vector3D constructor that takes another vector as a parameter and creates a copy.

3. Manually copy the three values yourself (b = new Vector3D(a.x, a.y, a.z)), if you cannot change the implementation of Vector3D.

Answer 3

You may want to change your Vector3D class to a struct. That would let you work with a value type instead of a reference type.

Your other option is to implement ICloneable or use some other method to create a deep copy of your object.