Why doesn't Java have a copy constructor?

java copy-constructor
Cuga picture Cuga · May 6, 2009 · Viewed 32.1k times · Source

Why doesn't Java support a copy constructor like in C++?

Answer

cletus picture cletus · May 6, 2009

Java does. They're just not called implicitly like they are in C++ and I suspect that's your real question.

Firstly, a copy constructor is nothing more than:

public class Blah {
  private int foo;

  public Blah() { } // public no-args constructor
  public Blah(Blah b) { foo = b.foo; }  // copy constructor
}

Now C++ will implicitly call the copy constructor with a statement like this:

Blah b2 = b1;

Cloning/copying in that instance simply makes no sense in Java because all b1 and b2 are references and not value objects like they are in C++. In C++ that statement makes a copy of the object's state. In Java it simply copies the reference. The object's state is not copied so implicitly calling the copy constructor makes no sense.

And that's all there is to it really.

Related questions

Clone() vs Copy constructor- which is recommended in java

clone method vs copy constructor in java. which one is correct solution. where to use each case?

Read More
Why do we need copy constructor and when should we use copy constructor in java

I was going through Copy Constructors, I have gone through the links in stack over flow and others as well. But i am not clear on the following points. Why do we need a Copy Constructor When do we need …

Read More
Proper way to deep copy with copy constructor instead of Object.clone

I have some code that performs a deep copy using Object.clone, but I'm trying to rewrite it using the more "acceptable" copy constructor technique. Below are two simple examples of what I'm trying to do, the first using clone …

Read More