This tutorial requires a basic understanding of variables, classes, and objects in the Java programming language.
Before starting this tutorial, please make sure to watch the 1301 review videos on eLC under "Content" -> "1301 Videos". Specifically, videos 14-22 will help you understand these concepts.
In computer programming, a variable is just an alias for a location in memory. Instead of requiring programmers to remember explicit memory addresses, we let them use variables as a matter of convenience. Every declared variable has the following:
- a value, the actual data stored in some memory location;
- a type, an attribute that tells the computer how to interpret the value and how much space is needed to store the value; and
- a name, an attribute that tells the computer the word that we want to use to refer to the associated data.
Take a moment to identify the value, type, and name of the variables declared and initialized below. Before looking ahead, write your answers in your notes.
int x = 17;
String s = "Hello!";
Did you come up with the answers below?
Declaration | Value | Type | Name |
---|---|---|---|
int x = 17 |
17 | int | x |
String s = "Hello" |
"Hello" | String | s |
Notice the type of the two variables above. The first, int
, is a primitive type and the second,
String
, is a reference type. You can immediately tell that String
is a reference type by the
fact that it start with a capital letter. These two variables both contain values but they work
very differently under the hood. In this tutorial, we will demonstrate the important
differences between these two types of variables.
In Java, the reference types (§4.3) are class types, interface types, and array types. Of these three, you are likely familiar with creating variables of both class and array types. Below are two examples:
Person ada; // A class type variable (valid only if we have a class called Person on the classpath)
double[] array; // An array type variable
Both of the above types are reference types which means that the variables contain the memory address (location) of the object that they refer to - not the object itself.
An object is really just a collection
of variables that are defined by a class. It is not uncommon to describe Java
objects as dynamically constructed instances of a class. When an object is
constructed, its collection of variables is stored contiguously in some location in
memory, which we usually call the object’s reference. This is
important because, in Java, the possible values of a reference type are
references to compatible objects (or null
).
Below we describe various scenarios in which you may encounter/use reference variables in your code.
Consider the following declaration and initialization:
Scanner s = null;
The variable s
has Scanner
as its type and null
as its value. In
Java, null
is a reference that can always be assigned or cast to any
reference type, and it is used to denote that no object is being
referred to. Therefore, we might say that s
does not currently refer
to any object.
Under the Hood: Remember,s
is an alias for some location in the
computer’s primary memory (RAM). Since we don’t know exactly where s
will be located when the program runs, we will use an arbitrary number
to denote this location. Here, we will use the value 800
(we could’ve
chosen any arbitrary value). The mapping of s
to a memory location all
happens under the hood and requires no explicit actions by the
programmer. The way this looks internally can be seen below. In the
diagram, we use 800
instead of s
since that’s what really happens in
the computer. Since we assigned null
to s
, the value at location
800
is null
.
800: [ null ]
Since using the variable name is more readable and doesn’t require us to choose an arbitrary address, it is more common to diagram this using the variable name:
+------+
s | null |
+------+
Now consider the following initialization:
Scanner s = new Scanner(System.in);
There is a lot happening on that line: i) the variable s
is declared
with Scanner
as its type; ii) a Scanner
object is constructed; then
iii) the object’s reference is assigned to s
. Since the value of s
is now a reference to some Scanner
object, we might say that s
refers to some Scanner
object.
Under the Hood: Let 800
again denote the memory location that
stores s
’s value and 12048
denote the memory location of the
constructed Scanner
object. Again, these values are arbitrary. The
diagram below demonstrates the values that are stored at these two
memory locations. Pay close attention to fact that 800
(or s
) does
not store the Scanner
object’s contents. Instead, s
is the address
where the Scanner
object resides in memory. Understanding this idea is
the key to understanding how reference variables work in Java.
800: [ 12048 ]
...
12048: [ scanner object contents ... ]
It is more common to diagram this using the variable name and an arrow
to the object (since we may not know or care what the actual value of
the memory address of s
):
+--+ +----------------+
s | -|----◆| |
+--+ | |
+----------------+
Important: When a method is called using s
(for example,
s.nextLine()
), the object that s
refers to is known as the calling
object. Non-static methods called using s
are said to operate on the
calling object. Since the reference in the value of s
can change over
time, the calling object can also change.
Now consider the following initializations:
Scanner s = new Scanner(System.in);
Scanner t = s;
Before moving on, take a moment to draw a diagram on a sheet of paper that shows how this looks under the hood. You can come up with any arbitrary memory addresses that you wish.
Your drawing should look very similar to the previous example with an
extra variable for t
that contains the same value as the variable s
.
We provide the more common version of this diagram below.
The first line is the same as in Example 2. On the second line: i) the
variable t
is declared with Scanner
as its type; ii) the value of
s
is retrieved by the computer; then iii) the value is assigned to
t
. Since the value of t
is now the same as the value of s
, we
might say that s
and t
both refer to the same Scanner
object.
+--+ +----------------+
s | -|----◆| |
+--+ | |
+----------------+
◆
+--+ |
t | -|-------+
+--+
This is an interesting scenario because the calling object for s
and
the calling object for t
are now the same object!
Consider the following reference type variable declaration:
SomeType varName;
The values that can be assigned to varName
are null
and any
reference to an object whose type is compatible with SomeType
. In
Java, a reference to an object of a particular type is always compatible
with a variable of the same type. Here are some examples:
Scanner scan = new Scanner(System.in); // same types
String str = "Hello"; // same types
Object references are also compatible with a variable when the type of that is a superclass or interface of the reference type being assigned. We will discuss this in more detail later in the semester once interfaces and inheritance are introduced.
When you invoke a constructor using new SomeClassName()
(or similar),
the type of the reference produced by the expression is the same as the
class name. This reference can be assigned to any compatible variable or
returned in any method with a compatible return type.
Feedback? Please help us make this better! If you have any feedback or suggestions for this reading or tutorial, then use the link below to reach the feedback form.
Copyright © Michael E. Cotterell, Bradley J. Barnes, and the University of Georgia. This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License to students and the public. The content and opinions expressed on this Web page do not necessarily reflect the views of nor are they endorsed by the University of Georgia or the University System of Georgia.