Understanding toString(), String.valueOf(), and Type Casting in Java

1. Introduction

The author introduces three common methods used in daily Java development—toString(), String.valueOf(), and explicit casting—explaining why each exists and when to choose the appropriate one.

2. Code Examples

1) Primitive Types

(1) Primitive types lack a toString() method.

(2) Recommended usage

(3) Cannot cast directly

Explicit casting of an Object to String should be preceded by an instanceof check to avoid ClassCastException.

2) Wrapper Types

(1) toString() works

(2) String.valueOf() works as well.

(3) Wrapper types also cannot be cast directly.

3) Null Value Issues

(1) toString() throws NullPointerException when the reference is null.

(2) String.valueOf() returns the string "null" for a null reference.

(3) Casting null to String succeeds but yields null.

3. Source Code Analysis

1) toString()

Analysis of the Object.toString() implementation and its behavior when overridden in subclasses.

2) String.valueOf()

String.valueOf() adds a null‑check before delegating to toString(), preventing NullPointerException.

4. Summary

1) toString() may throw NullPointerException.

Ensure the object is not null before calling toString(), or override it safely in subclasses.

2) String.valueOf() is recommended because it never throws NullPointerException and returns the literal "null" for null references.

3) Explicit casting (String) should be avoided unless an instanceof check confirms the object's type.

Using instanceof before casting helps prevent ClassCastException and makes the code more robust.