使用===而非==是避免PHP類型轉(zhuǎn)換陷阱的關(guān)鍵，因?yàn)?==同時(shí)比較值和類型，而==會(huì)進(jìn)行類型轉(zhuǎn)換導(dǎo)致意外結(jié)果。1. ==在類型不同時(shí)會(huì)自動(dòng)轉(zhuǎn)換，例如'hello'被轉(zhuǎn)為0，因此0 == 'hello'為true；2. ===要求值和類型都相同，避免了此類問題；3. 在處理strpos()返回值或區(qū)分false、0、''、null時(shí)必須使用===；4. 盡管==可用于用戶輸入比較等場景，但應(yīng)優(yōu)先顯式類型轉(zhuǎn)換并使用===；5. 最佳實(shí)踐是默認(rèn)使用===，避免依賴==的隱式轉(zhuǎn)換規(guī)則，確保代碼行為一致可靠。

PHP’s type juggling can be both a convenience and a trap—especially when comparing values using == versus ===. If you've ever been surprised by 0 == 'hello' returning true, you're not alone. Let’s break down exactly how PHP handles loose (==) and strict (===) comparisons, and why understanding the difference is crucial for writing reliable code.

What’s the Difference Between == and ===?

At a high level:

• == (loose comparison): Compares values after type juggling—PHP tries to convert types to match before comparing.
• === (strict comparison): Compares both value and type. No conversion happens.

0 == '0'     // true  – PHP converts string '0' to int 0
0 === '0'    // false – types differ: int vs string

That simple example shows why === is safer: it avoids surprises from automatic type conversion.

How PHP’s Loose Comparison (==) Actually Works

PHP follows a complex set of rules when using ==. These are defined in the PHP type comparison tables, but here’s what happens under the hood:

1. If types are the same, compare directly

No conversion needed:

5 == 5        // true (both int)
'hello' == 'hello' // true

2. If types differ, PHP tries to convert them

This is where things get weird. Common gotchas include:

• String to number conversion: If a string looks like a number, it gets converted.

  '123' == 123   // true
  '123abc' == 123 // false – can't fully convert
  '0abc' == 0     // true – '0abc' becomes 0 when cast to int

• Empty or zero-like strings become 0

  '0' == 0       // true
  '' == 0        // true
  ' ' == 0       // true (after trimming, becomes empty)

• Booleans are converted early

  true == '1'    // true
  true == 'any string' // true – because (bool)'any string' is true

• Null and empty string are "equal" to many things

  null == ''     // true
  null == 0      // true
  null == false  // true

• Arrays and objects have special behaviors

  array() == 0   // true
  array() == false // true

And the infamous:

0 == 'hello'   // true – because (int)'hello' is 0

Yes, really. 'hello' cast to integer becomes 0, so 0 == 0.

Why === Is Almost Always Safer

Strict comparison avoids all type coercion. It only returns true if:

• The values are equal
• The types are identical

0 === '0'      // false – int vs string
0 === 0        // true
'0' === '0'    // true
null === false // false – different types

This predictability makes === ideal for:

• Checking function return values (e.g., strpos())
• Validating input
• Working with false, 0, '', null, which are loosely equal but mean different things

Example: strpos() Gotcha

if (strpos('hello', 'x') == false) {
    echo "Not found";
}

This seems fine—but if the substring is found at position 0, strpos() returns 0, and 0 == false is true. So you get a false "not found".

? Correct version:

if (strpos('hello', 'x') === false) {
    echo "Not found";
}

Now it only triggers when truly not found.

When Is == Acceptable?

While === is generally recommended, == isn't evil—it has legitimate uses:

• Comparing user input where type doesn't matter:

  if ($_GET['page'] == 5) // whether '5' or 5, treat same

• Working with configuration values that may be strings
• Quick prototyping (but switch to === in production)

But even then, be cautious. Consider explicitly casting instead:

(int)$_GET['page'] === 5

This makes the intent clear and avoids ambiguity.

Summary: Best Practices

To avoid type juggling pitfalls:

• ? Use === and !== by default
• ? Never rely on loose comparison for false, 0, '', null
• ? Cast types explicitly when needed
• ? Test edge cases—especially strings that start with numbers
• ? Avoid == unless you fully understand the conversion rules

Type juggling in PHP can feel like magic—until it bites you. The == operator tries to be helpful, but its behavior is full of edge cases. By using ===, you take control and write code that behaves consistently, not coincidentally.

Basically: when in doubt, go strict.

Ce qui précède est le contenu détaillé de. pour plus d'informations, suivez d'autres articles connexes sur le site Web de PHP en chinois!