Talk:Object copying

Cleanup requested

Sorry, but this page seem jumbled up. The term Deep Copy can be explained without diving too deep into the specifics of one programming language (although an exame _can_ be C++ code). Going into copy constructors here doesn't seem to me like a good idea.

And what's with "The specification of C++ understandably frowns on changing t" ???

Ripper234 20:22, 2 April 2006 (UTC)

Hi, I changed the article a little bit. It was lacking the initial simple definition of the term so I added it. Plus I added an introduction for simple copies. That can be expanded to give examples of how overloading applies to object copying. Copy constructors ditto. It still needs to be improved. --Radacovsky 00:00, 27 October 2006 (UTC)

Hi

i have added an example code which describes the difference between deep and shallow copy to my understanding, please let me know any corrections in the code.

with regards krishnakishoremendi@yahoomail.com —Preceding unsigned comment added by Kk2mkk (talk • contribs) 14:34, 22 April 2008 (UTC)

Defensive copy

Defensive copy redirects to this article. What does it mean? --Abdull (talk) 23:56, 3 August 2010 (UTC)

Five years ago, when the redirect from defensive copy to object copy was created, the article contained the following text:[1]

Implementors may set up some copy constructors with reference counting so that identical copies of an object do not take up additional memory. This technique interacts badly with low-level access to internal object data. Defensive copy is an act to ensure that the object retains a state that exists at the moment of duplication.

Apparently, this text was removed in 2007.[2] — Tobias Bergemann (talk) 06:29, 4 August 2010 (UTC)

Utilities for Deep Copy

Is there a place on this page for utilities to simplify deep copying, like http://www.codeproject.com/KB/cs/generic_deep_cloning.aspx for C#, http://robust-it.co.uk/clone/ and http://www.genericdeepcopy.com for Java?

Currently at the end of the Java section there's the line "Another way to copy objects in Java is to serialize them..." It seems like the utility reference would fit in there or at the end..

I was thinking:

Some utilities attempt to simplify creating deep copies of objects with varying degrees of success.

thoughts? 24.9.229.231 (talk) 22:35, 14 August 2010 (UTC)