Primitive vs reference storage in Java - When to Use Which

The Big Idea

Ever wondered why changing one variable sometimes changes another unexpectedly? The answer lies in how data is stored!

The Scenario

Imagine you have a list of your friends' phone numbers and their addresses written on paper. You want to update a friend's address, but you only have their phone number written down. You try to change the address on the phone number list, but it doesn't work because the address is stored somewhere else.

The Problem

When you store data manually without understanding how it is saved, you might copy the phone number but not the address linked to it. This causes confusion and errors because changing one copy doesn't update the other. It's slow and frustrating to keep track of all copies and updates.

The Solution

Understanding primitive vs reference storage helps you know when you are working with actual data values (like phone numbers) or with references (like addresses pointing to a location). This way, you can update information correctly and avoid mistakes.

Before vs After

✗ Before

int a = 5;
int b = a;
b = 10; // a is still 5

String s1 = "hello";
String s2 = s1;
s2 = "world"; // s1 is still "hello"

✓ After

int a = 5;
int b = a;
b = 10; // a is still 5

StringBuilder sb1 = new StringBuilder("hello");
StringBuilder sb2 = sb1;
sb2.append(" world"); // sb1 is now "hello world"

What It Enables

This concept lets you control how data changes affect your program, making your code more predictable and easier to fix.

Real Life Example

When building a contact app, knowing if you are copying a phone number (primitive) or a contact object (reference) helps you decide if changing one contact updates all places where it's used or just one copy.

Key Takeaways

Primitives store actual values directly.

References store addresses pointing to objects.

Knowing the difference helps avoid bugs and manage data updates correctly.

Practice

1. Which of the following correctly describes how primitive types are stored in Java?

easy

A. They store values as strings internally.

B. They store the actual value directly in the variable.

C. They store the memory address of the variable.

D. They store a reference to an object in memory.

Solution

1. Step 1: Understand primitive storage

   Primitive types like int, double, and boolean store the actual data value directly in the variable's memory location.

2. Step 2: Compare with reference types

   Reference types store addresses pointing to objects, not the actual data value.

3. Final Answer:

   They store the actual value directly in the variable. -> Option B

4. Quick Check:

   Primitive = actual value [OK]

Hint: Primitives hold values; references hold addresses [OK]

Common Mistakes:

• Thinking primitives store memory addresses
• Confusing reference storage with primitive storage
• Assuming primitives store objects

2. Which of the following is the correct way to declare a reference variable for a String in Java?

easy

A. int s = new String();

B. boolean s = new String();

C. String s = 10;

D. String s = new String();

Solution

1. Step 1: Check variable type and assignment

   String is a reference type, so it can be assigned with new String() to create a new object.

2. Step 2: Verify type compatibility

   int and boolean are primitive types and cannot be assigned a String object.

3. Final Answer:

   String s = new String(); -> Option D

4. Quick Check:

   Reference declaration matches object creation [OK]

Hint: Reference types use 'new' with matching type [OK]

Common Mistakes:

• Assigning objects to primitive types
• Using incompatible types in declaration
• Missing 'new' keyword for object creation

3. What will be the output of the following code?

int a = 5;
int b = a;
b = 10;
System.out.println(a);

medium

A. 5

B. 10

C. 0

D. Compilation error

Solution

1. Step 1: Understand primitive assignment

   Variable b copies the value of a (which is 5). Changing b to 10 does not affect a.

2. Step 2: Print value of a

   Since a was not changed, printing a outputs 5.

3. Final Answer:

   5 -> Option A

4. Quick Check:

   Primitive copy keeps original value [OK]

Hint: Changing copied primitive doesn't affect original [OK]

Common Mistakes:

• Assuming a changes when b changes
• Confusing reference behavior with primitive
• Expecting compilation error

4. Consider the code below. What is the error and how to fix it?

String s1 = "hello";
String s2 = s1;
s2 = "world";
System.out.println(s1);

medium

A. Output is 'world' because s2 changes s1.

B. Error: Strings cannot be assigned like this.

C. No error; output is 'hello'.

D. Compilation error due to missing new keyword.

Solution

1. Step 1: Analyze reference assignment

   s2 points to the same String object as s1 initially, but assigning s2 = "world" makes s2 point to a new String object.

2. Step 2: Check effect on s1

   s1 still points to "hello" because Strings are immutable and s2 reassignment does not affect s1.

3. Final Answer:

   No error; output is 'hello'. -> Option C

4. Quick Check:

   Reference reassignment doesn't change original object [OK]

Hint: Reassigning reference doesn't change original object [OK]

Common Mistakes:

• Thinking s1 changes when s2 changes
• Expecting compilation error for String assignment
• Confusing mutable and immutable objects

5. Given the following code, what will be the output?

class Box {
  int value;
  Box(int v) { value = v; }
}

Box b1 = new Box(5);
Box b2 = b1;
b2.value = 10;
System.out.println(b1.value);

hard

A. 10

B. 5

C. Compilation error

D. NullPointerException

Solution

1. Step 1: Understand reference assignment for objects

   b2 is assigned the reference of b1, so both point to the same Box object.

2. Step 2: Modify object through b2

   Changing b2.value to 10 changes the single Box object's value.

3. Step 3: Print b1.value

   Since b1 points to the same object, b1.value is now 10.

4. Final Answer:

   10 -> Option A

5. Quick Check:

   Reference change affects original object [OK]

Hint: Object references share same data; change affects all [OK]

Common Mistakes:

• Assuming b1.value stays 5 after b2 changes it
• Confusing primitive and reference behavior
• Expecting compilation or runtime errors