46

Possible Duplicate:Is Java pass by reference?

public class myClass{    public static void main(String[] args){        myObject obj = new myObject("myName");        changeName(obj);        System.out.print(obj.getName()); // This prints "anotherName"    }    public static void changeName(myObject obj){        obj.setName("anotherName");    }}

I know that Java pass by value, but why does it passobj by reference in previous example and change it?

askedOct 25, 2011 at 17:44
MBZ's user avatar
2
  • 13
    This has been asked, like, a million times.CommentedOct 25, 2011 at 17:47
  • Your example illustrates a logic of what long time before Java was called "call be reference" or "object passed be reference". Now when it comes to Java, there is a congregation on an island with dogma "Java is pass by value" and according to this dogma they will twist the entire world to make this true, not to begin with "Java is pass by value" is a grammatical nonsense. According to the dogma e.g. an object is not a value, but a reference of an object is.CommentedFeb 15, 2022 at 22:34

6 Answers6

132

Java always passes arguments by value, NOT by reference. In your example, you are still passingobj by its value, not the reference itself. Inside your methodchangeName, you are assigning another (local) reference,obj, to the same object you passed it as an argument. Once you modify that reference, you are modifying the original reference,obj, which is passed as an argument.


EDIT:

Let me explain this through an example:

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 refers to!     }     public static void changeReference(Foo a)     {          Foo b = new Foo("b");          a = b;     }     public static void modifyReference(Foo c)     {          c.setAttribute("c");     }}

I will explain this in steps:

1- Declaring a reference namedf of typeFoo and assign it to a new object of typeFoo with an attribute"f".

Foo f = new Foo("f");

Enter image description here

2- From the method side, a reference of typeFoo with a namea is declared and it's initially assigned tonull.

public static void changeReference(Foo a)

Enter image description here

3- As you call the methodchangeReference, the referencea will be assigned to the object which is passed as an argument.

changeReference(f);

Enter image description here

4- Declaring a reference namedb of typeFoo and assign it to a new object of typeFoo with an attribute"b".

Foo b = new Foo("b");

Enter image description here

5-a = b is re-assigning the referencea NOTf to the object whose its attribute is"b".

Enter image description here


6- As you callmodifyReference(Foo c) method, a referencec is created and assigned to the object with attribute"f".

Enter image description here

7-c.setAttribute("c"); will change the attribute of the object that referencec points to it, and it's same object that referencef points to it.

Enter image description here

I hope you understand now how passing objects as arguments works in Java :)

Peter Mortensen's user avatar
Peter Mortensen
31.4k22 gold badges110 silver badges134 bronze badges
answeredOct 25, 2011 at 17:44
Eng.Fouad's user avatar
Sign up to request clarification or add additional context in comments.

7 Comments

thanks you alot, for explaining in details.
Now i got what "reference to obj as a value" or "sending copy of reference" means :)
The diagrams really helped make these concepts clear! Thank you!
This explanation is very clear, but I'm still a bit confused. In the step 3, "a" is pointing to an object whose attribute isf. To me, "a" seems to be pointing the reference of the object which "f" is pointing too. If objects are passed by values, both "a" and "f" should have their own objects. However, they are actually sharing the same objects (i.e. they are pointing to the reference of the same object).
@Hiroki Objects are not passed by value. It is the pointer to the object that is passed by value. Variables in Java cannot contain objects, they always contain a pointer to the object. And therefore, objects cannot be passed to methods, it is always the pointer to the object that is passed by value to the method.
|
9

In Java, an object handle, or the identity of an object is considered a value. Passing by value means passing this handle, not a full copy of the object.

A "reference" in the term "pass by reference" also doesn't mean "reference to an object". It means "reference to a variable" – a named "bucket" in a function definition (or, rather, a call frame) that can store a value.

Passing by reference would mean the called method could changevariable values in the calling method. (For example, in the C standard library, the functionscanf works this way.) This isn't possible in Java. You can always change theproperties of an object – they aren't considered a part of its "value". They're completely different independent objects.

answeredOct 25, 2011 at 17:53
millimoose's user avatar

6 Comments

I appreciated this answer as it explained that in Java an object property isn't considered part of its "value". But in my world, allowing a function or method with its own scope to modify a variable (or an object) that's outside its scope and in the calling method's scope is "pass by reference", sorry Java guys.
So what's your point? Different languages have different conceptual models, and different terminologies. As long as "your world" is not the Java world, or that of one of Java's relatives, it's not really relevant here, is it? I could just as well argue that PHP and Perl are the odd ones out by natively implementing "pass-by-deep-copy", but that's just semantics and not useful to anybody. Java's terminology is roughly consistent with how C works - the difference between passingfoo or&foo.
And in C++, another ancestor of Java, passing by reference as opposed to value again has no relation to whether a function is changing state not directly in the stack frame. That's whatconst is for. (Although given C++'s extraordinary flexibility, it's certainly possible for passing by value to copy an object however you wish.) In these languages, a reference more or less means a (local) variable that you canassign a value to and change state outside the current scope. Not merely any variable pointing to possibly non-local state.
It's really mostly about the level at which you think about things, and what you think is the "value" of a variable. At a low level, a Java variable is the name for the address of a tiny chunk of memory that contains, say, 8 bytes of data. (Java does not do stack-allocation of data structures, I don't think older versions of C did either, and PHP probably doesn't either.) This memory either contains a datum directly if it's a simple data type or an integer, or it contains another memory address of a bigger chunk of memory. When we talk about the value of the variable, we mean those 8 bytes.
thanks for the additional clarification, maybe minus the attitude. The other parts were helpful.
|
3

It did not change obj (your code doesn't change it anyway).Had it been passed by reference, you could have written:

public static void changeName(myObject obj){    obj = new myObject("anotherName");}

And have "anotherName" printed by the main method.

answeredOct 25, 2011 at 17:53
Maurice Perry's user avatar

1 Comment

Just a small remark: myObject should be MyObject.
2

You're changing aproperty ofobj, not changingobj (the parameter) itself.

The point is that if you pointedobj at something else inchangeName thatthat change would not be reflected inmain.

Seethis post for further clarification.

answeredOct 25, 2011 at 17:47
Dave Newton's user avatar

Comments

1

It is passing the reference to obj as a value (a bit confusing I know :)).

So let's say it makes a copy of the pointer to obj's value and pass that.

That means that you can do things like:

  public static void changeName(myObject obj){            obj.setName("anotherName");        obj = new myObject();    }

and the statement

System.out.print(obj.getName());

is still going to refer to the old object (the one that you did setName).

Peter Mortensen's user avatar
Peter Mortensen
31.4k22 gold badges110 silver badges134 bronze badges
answeredOct 25, 2011 at 17:53
Mikel's user avatar

1 Comment

Have not seen a definition of "reference" in contrast to "reference as value" and thus it remains unclear by what means an object is passed, 'cause the actual use case is ´passing an object to some method´, where the object is shared between caller and called method, where the reference appears as technical aspect, not really touching the semantics of a shared object.
0

Java is passing a copy of what you're passing to your function. When it is a primitive type - it will be the copy of a value. When it is an object - you're passing the reference copy. In you're code example you're modifying one of objects properties, but not the reference itself so the name will be changed. However when you'd like to assign new object to obj variable in changeName function, then you're changing reference, so outside obj will have an old value.

answeredOct 25, 2011 at 17:53
mmatloka's user avatar

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.