Why strict typing matters in PHP - Visual Breakdown

Concept Flow - Why strict typing matters

Start: Declare variables

↓

Assign values without strict typing

↓

Perform operations

↓

Unexpected results?

Yes No↓

Errors or bugs

↓

Enable strict typing

↓

PHP checks types strictly

↓

Errors caught early

↓

More reliable code

This flow shows how enabling strict typing in PHP helps catch errors early by checking variable types, leading to more reliable code.

Execution Sample

PHP

<?php
declare(strict_types=1);
function add(int $a, int $b): int {
  return $a + $b;
}
echo add(5, '10');

This PHP code adds two integers with strict typing enabled, showing an error if types don't match exactly.

Execution Table

Step	Code Line	Action	Type Check	Result/Output
1	declare(strict_types=1);	Enable strict typing	Strict mode ON	No output
2	function add(int $a, int $b): int	Define function with int params	Parameters must be int	No output
3	return $a + $b;	Add parameters	Both must be int	No output
4	echo add(5, '10');	Call function with int and string	Type error: string passed instead of int	Fatal error: Uncaught TypeError
5	-	Execution stops due to error	-	-

💡 Execution stops at step 4 because '10' is a string, not an int, causing a TypeError under strict typing.

Variable Tracker

Variable	Start	After call
$a	undefined	5 (int)
$b	undefined	'10' (string) - causes error

Key Moments - 2 Insights

Why does passing '10' as a string cause an error when strict typing is enabled?

Because the function expects an int parameter, and with strict typing on (see execution_table step 4), PHP does not convert types automatically and throws a TypeError.

What happens if strict typing is not enabled and we pass a string '10' to the add function?

Without strict typing, PHP converts '10' to int automatically, so the function works fine (no error), but this can hide bugs (not shown in this trace).

Visual Quiz - 3 Questions

Look at the execution table, what causes the program to stop at step 4?

A A TypeError because a string was passed instead of an int

B A syntax error in the function definition

C A missing return statement

D A runtime warning but execution continues

💡 Hint

Check the 'Type Check' and 'Result/Output' columns at step 4 in the execution table.

According to the variable tracker, what is the type of $b when the function is called?

A int

B string

C float

D undefined

💡 Hint

Look at the 'After call' column for $b in the variable tracker.

If strict typing was disabled, what would likely happen when calling add(5, '10')?

A The program would throw a TypeError

B The function would return a string concatenation

C The string '10' would be converted to int 10 and addition proceeds

D The program would crash immediately

💡 Hint

Refer to the key moments section about behavior without strict typing.

Concept Snapshot

PHP strict typing:
- Enable with declare(strict_types=1);
- Function params must match declared types exactly
- Passing wrong types causes TypeError
- Helps catch bugs early
- Without it, PHP converts types automatically

Full Transcript

This example shows why strict typing matters in PHP. When strict typing is enabled, PHP checks that function arguments match the declared types exactly. In the example, the add function expects two integers. Passing a string '10' causes a TypeError and stops execution. Without strict typing, PHP would convert '10' to integer 10 automatically, which can hide bugs. Strict typing helps catch these errors early, making code more reliable.