This week's book giveaway is in the
We're giving away four copies of a choice of
"Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac"
and have Joe Kissell on-line!
A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
Win a copy of
Take Control of Upgrading to Yosemite
Take Control of Automating Your Mac
this week in the
Avoid making a copy reference of an object
Joined: Jul 10, 2007
Jun 27, 2008 06:51:00
What is the best way to copy an object?
Using obj2 = obj1 would change the values in obj1 when I change them in obj2.
I do not want the second object to be a reference to the first object. Changes in object2 should not change object1.
Is the interface Cloneable the best way to do this?
Joined: Jun 01, 2007
Jun 27, 2008 07:11:00
You can make a copy constructor so that your code becomes
obj2 = new MyObject(obj1);
You then just implement the MyObject(MyObject o) constructor to perform the copy in whatever way is appropriate for your class.
Joined: Nov 08, 2007
Jun 27, 2008 11:03:00
there's a 100 answers to "which way is best", and the only correct ones include "it depends"
there's a lot written about it, you should be able to find by searching a bit,
in the mean time, the copy constructor above is a minimally invasive way to get a copy,
Bill Shirley - bshirley - frazerbilt.com
if (Posts < 30) you.read(
subject: Avoid making a copy reference of an object
Dan's GC Question Doubt
Khalid: GC ?
passing parameters to a method.
Khalid & Rasmussen 's gc stuff.....
one question about gc?
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2014