Limitations of PHP empty() Function and Proper Usage

Technical Limitations of empty() Function

In PHP versions prior to 5.5, developers frequently encountered a confusing error: "can't use method return value in write context". This error typically appears in code like:

if (!empty($r->getError()))

where getError() is a simple method:

public function getError()
{
    return $this->error;
}

Technical Principle Analysis

The root cause of this error lies in the design mechanism of the empty() function. empty() needs to access values by reference to check whether the reference points to an existing object. Before PHP 5.5, the language did not support creating references to temporary values returned from functions.

However, the deeper issue is developers' misunderstanding of the empty() function. empty() is essentially just an alias for !isset($thing) || !$thing. When the object being checked always exists (in PHP, results of function calls always exist), the empty() function is actually nothing more than a negation operator.

Equivalence Between empty() and Logical Negation

PHP doesn't have a true concept of 'emptiness'. Values that evaluate to false are considered empty, while values that evaluate to true are considered non-empty. These two expressions actually represent the same concept. Consider the following code:

$x = something();
if (empty($x)) …

versus:

$x = something();
if (!$x) …

In all cases, for all data types, these two approaches produce exactly the same results. Because $x is already defined, the use of empty() is redundant.

Characteristics of Method Return Values

Method return values always exist. Even without an explicit return statement, the return value exists and contains null. Therefore:

if (!empty($r->getError()))

is logically equivalent to:

if ($r->getError())

Solutions and Best Practices

Although PHP 5.5+ versions have resolved this technical limitation, the correct approach is to reconsider the necessity of using empty(). In most cases, directly using logical operators is a more concise and efficient choice.

Some developers might adopt the temporary variable solution:

$err = $r->getError();
if (!empty($err))

but this approach introduces unnecessary intermediate variables, increasing code complexity and memory usage.

Modern PHP Development Recommendations

In contemporary PHP development, it's recommended to:

1. Use direct logical evaluation instead of empty() for function or method return values
2. Understand the original design intent of empty() being suitable only for variable checks
3. Pay attention to cases where empty() is used on function return values during code review
4. Maintain code simplicity and readability by avoiding unnecessary function calls

By adopting these best practices, developers can not only avoid compatibility issues but also write clearer and more efficient PHP code.