Java is Pass-by-Value!

<!--blog template-->

<style type="text/css"> <!-- @page { margin: 2cm } P { margin-bottom: 0.21cm } H2 { margin-bottom: 0.21cm } H2.ctl { font-family: "Lohit Hindi" } PRE.cjk { font-family: "DejaVu Sans", monospace } H3 { margin-bottom: 0.21cm } H3.ctl { font-family: "Lohit Hindi" } A:link { so-language: zxx } --> </style> Introduction Pass-by-value The actual parameter (or argument expression) is fully evaluated and the resulting value is copied into a location being used to hold the formal parameter's value during method/function execution. That location is typically a chunk of memory on the runtime stack for the application (which is how Java handles it), but other languages could choose parameter storage differently. Pass-by-reference The formal parameter merely acts as an alias for the actual parameter. Anytime the method/function uses the formal parameter (for reading or writing), it is actually using the actual parameter. Java is strictly pass-by-value, exactly as in C. Read the Java Language Specification (JLS). It's spelled out, and it's correct. In http://java.sun.com/docs/books/jls/third_edition/html/classes.html#8.4.1: When the method or constructor is invoked (15.12) , the values of the actual argument expressions initialize newly created parameter variables, each of the declared Type, before execution of the body of the method or constructor. The Identifier that appears in the DeclaratorId may be used as a simple name in the body of the method or constructor to refer to the formal parameter. [In the above, values is my emphasis, not theirs] In short: Java has pointers and is strictly pass-by-value. There's no funky rules. It's simple, clean, and clear. (Well, as clear as the evil C++-like syntax will allow ;) Note: See the note at the end of this article for the semantics of remote method invocation (RMI). What is typically called "pass by reference" for remote objects is actually incredibly bad semantics. The Litmus Test There's a simple "litmus test" for whether a language supports pass-by-reference semantics: Can you write a traditional swap(a,b) method/function in the language? A traditional swap method or function takes two arguments and swaps them such that variables passed into the function are changed outside the function. Its basic structure looks like Figure 1: (Non-Java) Basic swap function structure If you can write such a method/function in your language such that calling Figure 2: (Non-Java) Calling the swap function actually switches the values of the variables var1 and var2, the language supports pass-by-reference semantics. For example, in Pascal, you can write Figure 3: (Pascal) Swap function or in C++ you could write Figure 4: (C++) Swap function (Please let me know if my Pascal or C++ has lapsed and I've messed up the syntax...) But you cannot do this in Java! Now the details... The problem we're facing here is statements like In Java, Objects are passed by reference, and primitives are passed by value. This is half incorrect. Everyone can easily agree that primitives are passed by value; there's no such thing in Java as a pointer/reference to a primitive. However, Objects are not passed by reference. A correct statement would be Object references are passed by value. This may seem like splitting hairs, bit it is far from it. There is a world of difference in meaning. The following examples should help make the distinction. In Java, take the case of Figure 5: (Java) Pass-by-value example the variable passed in (aDog) is not modified! After calling foo, aDog still points to the "Max" Dog! Many people mistakenly think/state that something like Figure 6: (Java) Still pass-by-value... shows that Java does in fact pass objects by reference. The mistake they make is in the definition of Figure 7: (Java) Defining a Dog pointer itself. When you write that definition, you are defining a pointer to a Dog object, not a Dog object itself. On Pointers versus References... The problem here is that the folks at Sun made a naming mistake. In programming language design, a "pointer" is a variable that indirectly tracks the location of some piece of data. The value of a pointer is often the memory address of the data you're interested in. Some languages allow you to manipulate that address; others do not. A "reference" is an alias to another variable. Any manipulation done to the reference variable directly changes the original variable. Check out the second sentence of http://java.sun.com/docs/books/jls/third_edition/html/typesValues.html#4.3.1. "The reference values (often just references ) are pointers to these objects, and a special null reference, which refers to no object" They emphasize "pointers" in their description... Interesting... When they originally were creating Java, they had "pointer" in mind (you can see some remnants of this in things like NullPointerException). Sun wanted to push Java as a secure language, and one of Java's advantages was that it does not allow pointer arithmetic as C++ does. They went so far as to try a different name for the concept, formally calling them "references". A big mistake and it's caused even more confusion in the process. There's a good explanation of reference variables at http://www.cprogramming.com/tutorial/references.html. (C++ specific, but it says the right thing about the concept of a reference variable.) The word "reference" in programming language design originally comes from how you pass data to subroutines/functions/procedures/methods. A reference parameter is an alias to a variable passed as a parameter. In the end, Sun made a naming mistake that's caused confusion. Java has pointers, and if you accept that, it makes the way Java behaves make much more sense. Calling Methods Calling Figure 8: (Java) Passing a pointer by value passes the value of d to foo; it does not pass the object that d points to! The value of the pointer being passed is similar to a memory address. Under the covers it may be a tad different, but you can think of it in exactly the same way. The value uniquely identifies some object on the heap. However, it makes no difference how pointers are implemented under the covers. You program with them exactly the same way in Java as you would in C or C++. The syntax is just slightly different (another poor choice in Java's design; they should have used the same -> syntax for de-referencing as C++). In Java, is exactly like C++'s Figure 10: (C++) A pointer And using Figure 11: (Java) Following a pointer and calling a method is exactly like C++'s Figure 12: (C++) Following a pointer and calling a method To sum up: Java has pointers, and the value of the pointer is passed in. There's no way to actually pass an object itself as a parameter. You can only pass a pointer to an object. Keep in mind, when you call Figure 13: (Java) Even more still passing a pointer by value you're not passing an object; you're passing a pointer to the object. For a slightly different (but still correct) take on this issue, please see http://www-106.ibm.com/developerworks/library/j-praxis/pr1.html. It's from Peter Haggar's excellent book, Practical Java.) A Note on Remote Method Invocation (RMI) When passing parameters to remote methods, things get a bit more complex. First, we're (usually) dealing with passing data between two independent virtual machines, whi