Error vs Exception in PHP - Visual Side-by-Side Comparison

Concept Flow - Error vs Exception in PHP

Start PHP Script

↓

Code Runs

↓

Error Occurs?

No→Continue Execution

Yes↓

Is it Exception?

No→Error Handling (Fatal or Warning)

Yes↓

Exception Thrown

↓

Catch Exception?

No→Script Stops

Yes↓

Handle Exception

↓

Continue or Exit Gracefully

PHP runs code and checks for errors. Errors may stop the script or warn. Exceptions can be caught and handled to keep script running.

Execution Sample

PHP

<?php
try {
  throw new Exception('Oops!');
} catch (Exception $e) {
  echo $e->getMessage();
}
?>

This code throws an exception and catches it to print the message instead of stopping the script.

Execution Table

Step	Action	Evaluation	Result
1	Start script	No error or exception yet	Script running
2	Enter try block	No error	Inside try
3	Throw Exception	Exception('Oops!') created	Exception thrown
4	Catch Exception?	Yes, catch block matches Exception	Catch block entered
5	Execute catch block	$e->getMessage() returns 'Oops!'	Output: Oops!
6	End script	No unhandled errors or exceptions	Script ends normally

💡 Script ends normally after handling the exception.

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
$e	undefined	Exception object created	Exception object caught	Exception object used in catch

Key Moments - 3 Insights

Why doesn't the script stop when an exception is thrown?

Because the exception is caught in the catch block (see execution_table step 4), so the script handles it and continues.

What happens if an error occurs but is not an exception?

PHP may stop the script or show a warning depending on error type, since errors are not caught like exceptions (see concept_flow step 'Is it Exception? No').

Can exceptions be thrown without try-catch blocks?

Yes, but if not caught, the script stops with a fatal error (see concept_flow step 'Catch Exception? No').

Visual Quiz - 3 Questions

Look at the execution_table, what is the output at step 5?

A Fatal error

B Oops!

C No output

D Exception object

💡 Hint

Check the 'Result' column at step 5 in execution_table.

At which step does the exception get caught?

A Step 3

B Step 5

C Step 4

D Step 6

💡 Hint

Look for 'Catch block entered' in the 'Result' column.

If the catch block was missing, what would happen?

A Script stops with fatal error

B Exception is ignored

C Script continues normally

D Error warning shown but script continues

💡 Hint

Refer to concept_flow step 'Catch Exception? No --> Script Stops'.

Concept Snapshot

PHP Errors and Exceptions:
- Errors are problems PHP detects (fatal, warning, notice).
- Exceptions are special errors you can throw and catch.
- Use try { ... } catch (Exception $e) { ... } to handle exceptions.
- Uncaught exceptions stop the script.
- Errors may stop or warn depending on severity.

Full Transcript

This visual execution shows how PHP handles errors and exceptions. The script starts and runs code inside a try block. When an exception is thrown, PHP looks for a matching catch block. If found, it runs the catch block code, allowing the script to continue. If no catch block exists, the script stops with a fatal error. Errors differ from exceptions; they may stop the script or show warnings depending on type. Exceptions provide a way to handle problems gracefully in PHP code.

Practice

1. Which statement best describes the difference between an Error and an Exception in PHP?

easy

A. Errors are serious problems that usually stop the script, while exceptions can be caught and handled.

B. Exceptions are more serious than errors and always stop the script immediately.

C. Errors can be caught with try-catch blocks, but exceptions cannot.

D. There is no difference; errors and exceptions are the same in PHP.

Solution

1. Step 1: Understand PHP error handling basics

   Errors usually indicate serious problems like syntax errors or memory issues that stop the script.

2. Step 2: Understand exceptions in PHP

   Exceptions are objects that can be caught and handled using try-catch blocks to keep the program running.

3. Final Answer:

   Errors are serious problems that usually stop the script, while exceptions can be caught and handled. -> Option A

4. Quick Check:

   Error stops script, Exception can be caught [OK]

Hint: Errors stop scripts; exceptions can be caught and handled [OK]

Common Mistakes:

• Thinking exceptions always stop the script
• Believing errors can be caught with try-catch
• Confusing errors and exceptions as identical

2. Which of the following is the correct syntax to catch an exception in PHP?

easy

A. try { /* code */ } catch (Exception $e) { /* handle */ }

B. catch (Exception $e) { /* handle */ } try { /* code */ }

C. try { /* code */ } except (Exception $e) { /* handle */ }

D. try: /* code */ catch (Exception $e): /* handle */ endtry;

Solution

1. Step 1: Recall PHP exception handling syntax

   PHP uses try { ... } catch (Exception $e) { ... } to handle exceptions.

2. Step 2: Identify correct syntax among options

   try { /* code */ } catch (Exception $e) { /* handle */ } matches the correct PHP syntax; others use wrong keywords or order.

3. Final Answer:

   try { /* code */ } catch (Exception $e) { /* handle */ } -> Option A

4. Quick Check:

   try-catch block syntax = try { /* code */ } catch (Exception $e) { /* handle */ } [OK]

Hint: Remember: try then catch with parentheses [OK]

Common Mistakes:

• Using 'except' instead of 'catch'
• Placing catch before try
• Using colon syntax which is invalid in PHP

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

try {
  throw new Exception('Oops!');
  echo 'No error';
} catch (Exception $e) {
  echo 'Caught: ' . $e->getMessage();
}

medium

A. Fatal error: Uncaught Exception

B. No error

C. Caught: Oops!

D. No output

Solution

1. Step 1: Understand the throw statement

   The code throws an Exception with message 'Oops!'. The line after throw is not executed.

2. Step 2: Catch block execution

   The catch block catches the Exception and echoes 'Caught: ' plus the message.

3. Final Answer:

   Caught: Oops! -> Option C

4. Quick Check:

   Exception thrown and caught outputs message [OK]

Hint: Throw stops try; catch runs and prints message [OK]

Common Mistakes:

• Expecting 'No error' to print
• Thinking throw causes fatal error without catch
• Ignoring that catch block runs after throw

4. Identify the error in this PHP code snippet:

try {
  echo 10 / 0;
} catch (Exception $e) {
  echo 'Error caught';
}

medium

A. Syntax error: missing semicolon after echo.

B. Division by zero error is not caught because it is an Error, not an Exception.

C. Catch block syntax is incorrect.

D. No error; code runs and prints 'Error caught'.

Solution

1. Step 1: Understand division by zero in PHP

   Division by zero triggers a fatal Error, not an Exception.

2. Step 2: Check catch block behavior

   Catch block only catches Exceptions, so the Error is not caught and script stops.

3. Final Answer:

   Division by zero error is not caught because it is an Error, not an Exception. -> Option B

4. Quick Check:

   Errors not caught by catch(Exception) [OK]

Hint: Errors like division by zero aren't caught by catch(Exception) [OK]

Common Mistakes:

• Assuming catch catches all errors
• Thinking division by zero throws Exception
• Ignoring difference between Error and Exception

5. You want to handle both Error and Exception in PHP to prevent your script from stopping unexpectedly. Which approach is best?

hard

A. Use set_exception_handler() to catch both errors and exceptions.

B. Only use try-catch blocks everywhere; errors will be caught automatically.

C. Ignore errors and exceptions; PHP will handle them internally.

D. Use try-catch for exceptions and set a custom error handler with set_error_handler() for errors.

Solution

1. Step 1: Understand handling exceptions

   Exceptions are handled with try-catch blocks to catch and manage them.

2. Step 2: Understand handling errors

   Errors are handled by setting a custom error handler using set_error_handler() to manage errors gracefully.

3. Final Answer:

   Use try-catch for exceptions and set a custom error handler with set_error_handler() for errors. -> Option D

4. Quick Check:

   Separate handlers for errors and exceptions [OK]

Hint: Use try-catch for exceptions, set_error_handler for errors [OK]

Common Mistakes:

• Expecting try-catch to catch all errors
• Ignoring errors leading to script termination
• Using set_exception_handler for errors