If Java uses the pass-by reference, why won't a swap function work?
Your question demonstrates a common error made by Java language newcomers. Indeed, even seasoned veterans find it difficult
to keep the terms straight.
Java does manipulate objects by reference, and all object variables are references. However, Java doesn't pass method arguments by reference; it passes them by value.
Take the badSwap() method for example:
public void badSwap(int var1, int var2)
{
int temp = var1;
var1 = var2;
var2 = temp;
}
When badSwap() returns, the variables passed as arguments will still hold their original values. The method will also fail if we change
the arguments type from int to Object, since Java passes object references by value as well. Now, here is where it gets tricky:
public void tricky(Point arg1, Point arg2)
{
arg1.x = 100;
arg1.y = 100;
Point temp = arg1;
arg1 = arg2;
arg2 = temp;
}
public static void main(String [] args)
{
Point pnt1 = new Point(0,0);
Point pnt2 = new Point(0,0);
System.out.println("X: " + pnt1.x + " Y: " +pnt1.y);
System.out.println("X: " + pnt2.x + " Y: " +pnt2.y);
System.out.println(" ");
tricky(pnt1,pnt2);
System.out.println("X: " + pnt1.x + " Y:" + pnt1.y);
System.out.println("X: " + pnt2.x + " Y: " +pnt2.y);
}
If we execute this main() method, we see the following output:
X: 0 Y: 0 X: 0 Y: 0 X: 100 Y: 100 X: 0 Y: 0
The method successfully alters the value of pnt1, even though it is passed by value; however, a swap of pnt1 and pnt2 fails! This is the major source of confusion. In the main() method, pnt1 and pnt2 are nothing more than object references. When you pass pnt1 and pnt2 to the tricky() method, Java passes the references by value just like any other parameter. This means the references passed to the method
are actually copies of the original references. Figure 1 below shows two references pointing to the same object after Java passes an object to
a method.

Figure 1. After being passed to a method, an object will have at least two references
Java copies and passes the reference by value, not the object. Thus, method manipulation will alter the objects, since the references point to the original objects. But since the references are copies, swaps will fail. As Figure 2 illustrates, the method references swap, but not the original references. Unfortunately, after a method call, you are left with only the unswapped original references. For a swap to succeed outside of the method call, we need to swap the original references, not the copies.

Figure 2. Only the method references are swapped, not the original ones
Think of them as pointersBy Anonymous on May 29, 2009, 7:11 amRemember those variables you use, are realy POINTERS to objects, and all java pases by values. So, you just pass pointers by value. You can modify the object (since...
Reply | Read entire comment
it passes object reference in values (address)By Anonymous on March 21, 2009, 6:46 pmIt does pass the reference (address) but only the values of the reference. So the changes in the called method will reflect in the object in the calling area. ...
Reply | Read entire comment
Not exactly tightBy Anonymous on March 2, 2009, 6:13 amIf java do "by Value" pass arguments. How about this: MyClass a = new MyClass(...); foo(MyClass a) { a.DoSomeChange()...//which will change some attibute of...
Reply | Read entire comment
Better explained hereBy Anonymous on February 27, 2009, 3:59 pmBetter explained here
Reply | Read entire comment
In response to "Most of theBy Paul on February 26, 2009, 3:53 amIn response to "Most of the programmers need the passByRef", I'd like to suggest that passing by reference is an old fashioned bad habit which Java has sought to...
Reply | Read entire comment
View all comments