Platinum Partner
news,architects,nosql,architecture,pass by value

Java is Pass by Value and Not Pass by Reference

There has been a good amount of debate on whether "Java is pass by value or pass by reference?". Well, lets conclude it last time, Java is pass by value and not pass by reference. If it had been pass by reference, we should have been able to C like swaping of objects, but we can't do that in java. We know it already, right? When you pass a instance to a method, its memory address are copied bit by bit to new reference variable, thus both pointing to same instance. But if you change the reference inside method, original reference will not get chnage. If it was pass by reference, then it would have got changed also.

To prove it, lets see how memory allocations happen in runtime. It should solve the slightest doubts, if any. I am using following program for demonstration of the concept.

public class Foo
{
	private String attribute;
	
	public Foo (String a){
		this.attribute = a;
	}
	public String getAttribute() {
		return attribute;
	}
	public void setAttribute(String attribute) {
		this.attribute = attribute;
	}
}

public class Main
{
     public static void main(String[] args){
          Foo f = new Foo("f");
          changeReference(f); // It won't change the reference!
          modifyReference(f); // It will change the object that the reference variable "f" refers to!
     }
     public static void changeReference(Foo a) {
          Foo b = new Foo("b");
          a = b;
     }
     public static void modifyReference(Foo c) {
          c.setAttribute("c");
     }
}



Lets see what happen on runtime step by step :

1) Foo f = new Foo("f");

This statement will create a instance of class Foo, with 'attribute' initialized to 'f'. The reference to this created instance is assigned to variable f;



2) public static void changeReference(Foo a)

When this executes then a reference of type Foo with a name a is declared and it's initially assigned to null.



3) changeReference(f);

As you call the method changeReference, the reference a will be assigned to the object which is passed as an argument.



4) Foo b = new Foo("b"); inside first method

This will do exactly the same as in fisrt step, and will create a new instance of Foo, and assign it to b;



5) a = b;

This is the important point. Here, we have three reference variables and when statement executes, a and b will point to same instance created inside the method. Note: f is unchanged and it continuely pointing to instance, it was pointing originally. NO CHANGE !!



6) modifyReference(Foo c);

Now when this statement executed a reference, c is created and assigned to the object with attribute "f".



7) c.setAttribute("c");

This will change the attribute of the object that reference c points to it, and it's same object that reference f points to it.



I hope that this explanation was enough clear to make your understanding better, if it was not already.

Happy Learning !!

Published at DZone with permission of {{ articles[0].authors[0].realName }}, DZone MVB. (source)

Opinions expressed by DZone contributors are their own.

{{ tag }}, {{tag}},

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}
{{ parent.authors[0].realName || parent.author}}

{{ parent.authors[0].tagline || parent.tagline }}

{{ parent.views }} ViewsClicks
Tweet

{{parent.nComments}}