Here’s the “proper way” to do comparisons—and why it matters.

If you’re new to PHP, here’s the “proper way” to do comparisons—and why it matters.

1) Default to strict comparisons (=== and !==)
Strict comparisons check both value AND type. That prevents PHP from “helpfully” converting values behind your back. Loose comparisons (==) can make things like 0, "0", false, null, and "" behave as if they’re the same, which is a fast path to confusing bugs (and occasionally security issues).

2) Normalize types at the edges
Most weird comparison bugs come from comparing untrusted/unknown types: request input (strings), JSON (mixed), DB values (strings/ints depending on driver), etc. A good habit is to convert inputs into the types your app actually uses as early as possible (cast IDs to int, trim strings, parse booleans, validate numbers). Once everything is normalized, comparisons become boring—and boring is good.

3) Use strict mode for array lookups
For membership/search checks, always use the strict flag:
- in_array($needle, $haystack, true)
- array_search($needle, $haystack, true)
Without that third parameter, PHP will do loose comparisons and you can get accidental matches (especially with 0/"0"/false/null/"").

4) Be explicit in validation and auth logic
Avoid “truthy/falsey” shortcuts in important code. Instead of “if ($x == false)” or relying on empty(), write what you mean:
- $x === null
- $x === ''
- is_numeric($x)
- ctype_digit($x)
- filter_var($x, FILTER_VALIDATE_EMAIL), etc.
It reads clearer and behaves consistently.

Rule of thumb: if you care about correctness and predictability (you do), compare strictly, normalize inputs early, and make checks explicit—especially anywhere related to permissions, money, or data integrity.

Hoping to help bring new life back, this forum used to be poppin! Make DP the greatest again!