Type declarations for parameters in PHP - Step-by-Step Execution

Concept Flow - Type declarations for parameters

Function called with arguments

↓

Check each parameter type

↓

Type matches

↓

Use value

↓

Function body executes

↓

Return result or end

When a function is called, PHP checks if the arguments match the declared types. If they do, the function runs; if not, an error occurs.

Execution Sample

PHP

<?php
declare(strict_types=1);
function greet(string $name) {
  return "Hello, $name!";
}
echo greet("Alice");
?>

This code defines a function that requires a string parameter and prints a greeting.

Execution Table

Step	Action	Parameter	Passed Value	Type Check Result	Function Output
1	Function greet called	$name	"Alice"	string matches string
2	Inside function	$name	"Alice"	Valid	"Hello, Alice!"
3	Function returns				"Hello, Alice!"
4	Output printed				Hello, Alice!

💡 Function ends after returning the greeting string.

Variable Tracker

Variable	Start	After call	Final
$name	undefined	"Alice"	"Alice"

Key Moments - 2 Insights

What happens if we pass a number instead of a string to greet()?

PHP will throw a TypeError because the parameter $name expects a string, as shown in the type check step in the execution_table.

Can we omit the type declaration and still pass any value?

Yes, if no type is declared, PHP accepts any type, but you lose the safety of type checking, which can cause bugs later.

Visual Quiz - 3 Questions

Look at the execution_table, what is the type check result when greet is called with "Alice"?

A Type mismatch error

B No type declared

C string matches string

D Integer matches string

💡 Hint

Check the 'Type Check Result' column in the first row of execution_table.

At which step does the function return the greeting string?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the 'Function Output' column to find when the return happens.

If we remove the type declaration from the parameter, what changes in the execution?

A Type check step is skipped

B Function will always error

C Parameter becomes integer automatically

D Function output changes

💡 Hint

Refer to the 'Type Check Result' column and think about what happens without type declarations.

Concept Snapshot

Type declarations specify what type a function parameter must be.
PHP checks argument types when the function is called.
If types don't match, PHP throws an error.
If no type is declared, any type is accepted.
This helps catch bugs early and makes code clearer.

Full Transcript

This visual trace shows how PHP checks parameter types when calling a function with type declarations. The function greet requires a string parameter named $name. When called with "Alice", PHP confirms the argument is a string, allowing the function to run and return a greeting. If a wrong type is passed, PHP would throw a TypeError. Without type declarations, PHP accepts any type but loses safety. Tracking the variable $name shows it holds the passed string during execution. This helps beginners understand how PHP enforces types for function parameters step-by-step.

Practice

1. What does a type declaration for a function parameter in PHP do?

easy

A. It tells PHP what kind of data the function expects for that parameter.

B. It changes the function's return type automatically.

C. It makes the function run faster by optimizing memory.

D. It hides the parameter from being accessed outside the function.

Solution

1. Step 1: Understand the purpose of type declarations

   Type declarations specify the expected data type for function parameters, helping PHP check inputs.

2. Step 2: Identify what type declarations do not do

   They do not change return types, optimize speed, or hide parameters.

3. Final Answer:

   It tells PHP what kind of data the function expects for that parameter. -> Option A

4. Quick Check:

   Type declarations = specify expected parameter type [OK]

Hint: Type declarations specify expected input types for functions [OK]

Common Mistakes:

• Thinking type declarations change return types
• Believing they improve speed directly
• Confusing parameter visibility with type declarations

2. Which of the following is the correct syntax to declare a function parameter as an integer in PHP?

easy

A. function add(integer $a, integer $b) {}

B. function add($int a, $int b) {}

C. function add(int: $a, int: $b) {}

D. function add(int $a, int $b) {}

Solution

1. Step 1: Recall PHP type declaration syntax

   PHP uses the type name followed by the parameter with a $ sign, like int $a.

2. Step 2: Check each option's syntax

   function add(int $a, int $b) {} matches correct syntax. Options A, B, and D use invalid syntax.

3. Final Answer:

   function add(int $a, int $b) {} -> Option D

4. Quick Check:

   Correct syntax = type before $parameter [OK]

Hint: Type before $parameter name, no extra symbols [OK]

Common Mistakes:

• Putting $ before type name
• Using 'integer' instead of 'int'
• Adding colons or extra symbols

3. What will be the output of this PHP code?

function multiply(float $x, float $y) {
    return $x * $y;
}
echo multiply(3, 4.5);

medium

A. 13.5

B. 12

C. TypeError

D. 7.5

Solution

1. Step 1: Understand parameter types and argument passing

   The function expects floats. PHP will convert integer 3 to float 3.0 automatically.

2. Step 2: Calculate the multiplication

   3.0 * 4.5 = 13.5, so the function returns 13.5.

3. Final Answer:

   13.5 -> Option A

4. Quick Check:

   3 * 4.5 = 13.5 [OK]

Hint: PHP auto-converts int to float if declared [OK]

Common Mistakes:

• Expecting TypeError for int passed to float
• Calculating wrong multiplication
• Confusing output with integer result

4. Identify the error in this PHP function declaration:

function greet(string name) {
    return "Hello, $name!";
}

medium

A. Wrong type declaration keyword

B. Function must return int

C. Missing $ before parameter name

D. No error, code is correct

Solution

1. Step 1: Check parameter syntax

   In PHP, parameter names must start with a $ sign, so string name is incorrect.

2. Step 2: Identify the correct syntax

   The correct syntax is string $name with $ before the parameter name.

3. Final Answer:

   Missing $ before parameter name -> Option C

4. Quick Check:

   Parameter names need $ [OK]

Hint: Parameter names always start with $ in PHP [OK]

Common Mistakes:

• Omitting $ before parameter name
• Confusing type declaration with variable name
• Assuming no $ needed in function parameters

5. Given this function:

function process(array $data, int $limit = 10) {
    return array_slice($data, 0, $limit);
}

Which call will cause a TypeError?

hard

A. process([1, 2, 3], 2)

B. process('not an array', 5)

C. process([1, 2, 3])

D. process([1, 2, 3], 0)

Solution

1. Step 1: Analyze parameter types and defaults

   The first parameter must be an array; the second is an int with default 10.

2. Step 2: Check each call

   process([1, 2, 3], 2) passes array and int correctly. process('not an array', 5) passes a string instead of array, causing TypeError. Options A, B, and C pass valid types.

3. Final Answer:

   process('not an array', 5) causes TypeError -> Option B

4. Quick Check:

   First param must be array, string causes error [OK]

Hint: Check argument types match declared parameter types [OK]

Common Mistakes:

• Passing wrong type for array parameter
• Assuming default values fix type errors
• Ignoring parameter order and types