5.Understanding Java References, Memory, and Optional

Core Confusion

If text and textOp both point to memory location A, when text = null happens, doesn’t memory location A get updated to null, causing textOp to also become null?

The Analogy: Two Sticky Notes

To understand why textOp remains unaffected, think of it using a real-world analogy:

1. Memory Location A is a physical house.
2. Sticky Note 1 is your local variable text.
3. Sticky Note 2 is the internal reference field inside your textOp object.

When you write Optional.of(text), you are copying the address of House A onto both Sticky Note 1 and Sticky Note 2. At this point, both notes point to the exact same house.

When you write text = null, you take Sticky Note 1, cross out the address, and write null on it.

What happens to Sticky Note 2?

Nothing! Changing what is written on Sticky Note 1 has zero effect on Sticky Note 2. Sticky Note 2 still has the original address of House A written on it.

---

Step-by-Step Breakdown

1. Will textOp refer to memory location A?

Yes, absolutely. When you call Optional.of(text), Java copies the value of the reference stored in text (the memory address pointing to location A) and stores that copy inside the textOp object. Both variables independently hold that address.

2. When text = null, is memory location A updated with null?

No. Memory location A is never touched, modified, or overwritten.

Writing text = null only changes what the local variable text points to. It tells the local variable: “Stop holding the address of location A; instead, hold nothing (null).” The object living at location A remains completely safe and untouched.

3. Won’t textOp evaluate to null then?

No. Because textOp holds its own independent copy of the reference, reassigning the local variable text cannot alter the reference stored inside textOp.

Therefore:

• text now evaluates to null.
• textOp still points to the valid object at location A, so textOp.isPresent() continues to evaluate to true.