Multiple catch blocks in PHP - Mini Project: Build & Apply

Handling Errors with Multiple Catch Blocks in PHP

📖 Scenario: Imagine you are writing a PHP script that processes user input for a simple calculator. The input might cause different types of errors, such as division by zero or invalid input format. You want to handle these errors gracefully using multiple catch blocks.

🎯 Goal: Build a PHP script that uses try and catch blocks to handle different exceptions separately. You will create a function that divides two numbers and catches DivisionByZeroError and TypeError with different messages.

📋 What You'll Learn

Create a function called divide that takes two parameters: $a and $b.

Inside the function, perform the division $a / $b inside a try block.

Use multiple catch blocks to handle DivisionByZeroError and TypeError exceptions separately.

Print different error messages for each exception type.

Call the divide function with different inputs to test the error handling.

💡 Why This Matters

🌍 Real World

Handling different errors separately helps make programs more reliable and user-friendly, especially when dealing with user input or external data.

💼 Career

Understanding multiple catch blocks is important for writing robust PHP applications that can gracefully handle various runtime errors.

1

Create the divide function with parameters

Write a PHP function called divide that takes two parameters: $a and $b. Inside the function, start a try block but do not add any code inside it yet.

PHP

<?php

function divide($a, $b) {
    try {
        // Your code here
    }
}

Hint

Define the function with function divide($a, $b) and add a try block inside it.

2

Add division inside the try block

Inside the try block of the divide function, write code to return the result of $a / $b.

PHP

<?php

function divide($a, $b) {
    try {
        // Your code here
    }
}

Hint

Use return $a / $b; inside the try block.

3

Add multiple catch blocks for error handling

Add two catch blocks after the try block in the divide function. The first catch should catch DivisionByZeroError and print "Error: Division by zero.". The second catch should catch TypeError and print "Error: Invalid input type.".

PHP

<?php

function divide($a, $b) {
    try {
        return $a / $b;
    } catch (DivisionByZeroError $e) {
        // Your code here
    } catch (TypeError $e) {
        // Your code here
    }
}

Hint

Use two catch blocks: one for DivisionByZeroError and one for TypeError, each printing the correct message.

4

Call the divide function and print results

Call the divide function three times with these inputs: 10, 2, 5, 0, and "a", 3. Print the result or error message for each call on a new line using echo.

PHP

<?php

function divide($a, $b) {
    try {
        return $a / $b;
    } catch (DivisionByZeroError $e) {
        echo "Error: Division by zero.";
    } catch (TypeError $e) {
        echo "Error: Invalid input type.";
    }
}

// Your code here

Hint

Call divide(10, 2), divide(5, 0), and divide("a", 3). Print each result followed by a newline.

Practice

1.

What is the main purpose of using multiple catch blocks in PHP?

easy

A. To handle different types of exceptions separately

B. To run multiple try blocks at once

C. To catch errors without specifying the type

D. To speed up the program execution

Solution

1. Step 1: Understand the role of catch blocks

   Catch blocks are used to handle exceptions that occur in the try block.

2. Step 2: Recognize the benefit of multiple catch blocks

   Multiple catch blocks allow handling different exception types in different ways, improving error management.

3. Final Answer:

   To handle different types of exceptions separately -> Option A

4. Quick Check:

   Multiple catch blocks = different exception handling [OK]

Hint: Multiple catch blocks handle specific exceptions separately [OK]

Common Mistakes:

• Thinking multiple catch blocks run in parallel
• Believing catch blocks catch all errors without type
• Assuming multiple catch blocks improve speed

2.

Which of the following is the correct syntax to catch multiple exceptions in PHP?

try {
    // code
} catch (ExceptionType1 $e) {
    // handle
} catch (ExceptionType2 $e) {
    // handle
}

easy

A. try { } catch ExceptionType1, ExceptionType2 { }

B. try { } catch (ExceptionType1 $e, ExceptionType2 $e) { }

C. try { } catch (ExceptionType1 $e) { } catch (ExceptionType2 $e) { }

D. try { } catch (ExceptionType1 $e | ExceptionType2 $e) { }

Solution

1. Step 1: Review PHP multiple catch block syntax

   PHP uses separate catch blocks for each exception type, each with its own parentheses.

2. Step 2: Identify the correct syntax

   try { } catch (ExceptionType1 $e) { } catch (ExceptionType2 $e) { } shows two separate catch blocks, which is the correct way to catch multiple exceptions.

3. Final Answer:

   try { } catch (ExceptionType1 $e) { } catch (ExceptionType2 $e) { } -> Option C

4. Quick Check:

   Separate catch blocks = correct syntax [OK]

Hint: Use separate catch blocks for each exception type [OK]

Common Mistakes:

• Trying to catch multiple exceptions in one catch parentheses
• Using commas or pipes inside catch parentheses incorrectly
• Missing parentheses around exception type and variable

3.

What will be the output of the following PHP code?

try {
    throw new InvalidArgumentException("Invalid argument!");
} catch (RuntimeException $e) {
    echo "Runtime error caught";
} catch (InvalidArgumentException $e) {
    echo "Invalid argument caught";
}

medium

A. Invalid argument caught

B. Runtime error caught

C. No output, exception not caught

D. Fatal error

Solution

1. Step 1: Identify the thrown exception type

   The code throws an InvalidArgumentException.

2. Step 2: Match the thrown exception with catch blocks

   The first catch block is for RuntimeException, which does not match. The second catch block matches InvalidArgumentException, so it runs.

3. Final Answer:

   Invalid argument caught -> Option A

4. Quick Check:

   Exception type matches second catch block [OK]

Hint: Exception matches first compatible catch block [OK]

Common Mistakes:

• Assuming first catch block always runs
• Confusing exception types
• Expecting no output if first catch fails

4.

Find the error in this PHP code snippet:

try {
    // some code
} catch (Exception $e) {
    echo "General exception";
} catch (InvalidArgumentException $e) {
    echo "Invalid argument";
}

medium

A. Missing semicolon after catch blocks

B. Try block is empty, causing syntax error

C. InvalidArgumentException cannot be caught separately

D. The catch blocks are in wrong order; specific exceptions must come first

Solution

1. Step 1: Understand catch block order importance

   More specific exceptions must be caught before more general ones to avoid unreachable code.

2. Step 2: Identify the order problem

   The general Exception catch block is first, so the InvalidArgumentException catch block is unreachable and causes an error.

3. Final Answer:

   The catch blocks are in wrong order; specific exceptions must come first -> Option D

4. Quick Check:

   Specific catch before general catch [OK]

Hint: Place specific catch blocks before general ones [OK]

Common Mistakes:

• Putting general catch before specific catch
• Ignoring unreachable catch block warnings
• Assuming order does not matter

5.

Consider this PHP code:

try {
    if (rand(0,1)) {
        throw new RuntimeException("Runtime issue");
    } else {
        throw new InvalidArgumentException("Invalid argument");
    }
} catch (InvalidArgumentException | RuntimeException $e) {
    echo "Caught: " . $e->getMessage();
} catch (Exception $e) {
    echo "General exception";
}

What will this code output?

hard

A. No output

B. Caught: Runtime issue or Caught: Invalid argument

C. Syntax error due to multiple exceptions in one catch

D. General exception

Solution

1. Step 1: Understand combined catch block syntax

   PHP 7.1+ allows catching multiple exceptions in one catch using the pipe (|) symbol.

2. Step 2: Analyze thrown exceptions and matching catch

   Either RuntimeException or InvalidArgumentException is thrown randomly. Both are caught by the combined catch block, which prints the message.

3. Step 3: Confirm no syntax error

   The combined catch syntax is valid, so no syntax error occurs.

4. Final Answer:

   Caught: Runtime issue or Caught: Invalid argument -> Option B

5. Quick Check:

   Combined catch handles both exceptions [OK]

Hint: Use | to catch multiple exceptions in one block [OK]

Common Mistakes:

• Thinking multiple exceptions in one catch cause syntax error
• Expecting general exception catch to run first
• Ignoring random exception thrown