learning C# ... about objects and the = oper

            Poop x = new Poop(6);
            Poop y = new Poop(123);
           
            x.Print();  // output is 6
            y.Print();  // output is 123
           
            x = y;      // was object copied from y to x?
            x.Print();  // output is 123
            y.Print();  // output is 123
           
            y.P = 5555; // well, let's see...
            x.Print();  // output is 5555 *
            y.Print();  // output is 5555
           
                        // no -- x now references same object that y is
// so objects are treated as pointers... no biggie
            //  ... but how do I use = in a "copy" kind of way?

>>1
Protip: YOU DON'T!

Implement a clone() method that constructs and returns a new object with all the fields set to the same as the object to be cloned.

Or use immutable objects to the point becomes moot. <3 immutable objects.

Like... WTF, no automatic way to copy an object?

What do you think this is, C++?

>>5
A language
It should have features
Features would include copying objects

The language can't perform an automatic, intelligent deep copy any more than C++ can.  That's why C++ requires implementation of copy constructors, and that's why C# requires implementation of a clone method or a copy constructor.

Oh lawd is dat some operator overloading

def = o
    o = self
end

>>9
Infinite recursion?

a=a

>>9
Infinately retarded?

Yeah c++ would need a deep copy explicitly written out.  Don't know c# because you fail at it

Terrible!

Terrible!

Terrible!

Terrible[i]![/i]

Hi, I can spam /prog/ too, you faggot.

Also, smoke weed everyday.

18 Name: Anonymous 2011-02-04 14:58

19 Name: Anonymous 2012-03-28 2:21

my farts burn my anus
it hurts
in a good way

---

Don't change these.

Name:		Email:
Entire Thread Thread List