Why error handling uses rescue in Ruby - Quick Recap

Recall & Review

beginner

What does the rescue keyword do in Ruby?

rescue catches errors (exceptions) that happen in a block of code and lets the program handle them without crashing.

beginner

Why is error handling important in programming?

It helps the program keep running smoothly even when unexpected problems happen, like wrong input or missing files.

beginner

How does rescue improve user experience?

By catching errors, rescue allows the program to show friendly messages or fix issues instead of crashing suddenly.

beginner

What happens if you don't use rescue and an error occurs?

The program stops immediately and shows an error message, which can confuse users or cause data loss.

intermediate

Can rescue handle different types of errors?

Yes, you can specify which errors to catch or use a general rescue to catch all exceptions.

What is the main purpose of rescue in Ruby?

A To catch and handle errors

B To create new variables

C To loop through arrays

D To define methods

rescue is used to catch errors and prevent the program from crashing.

What happens if an error is not rescued in Ruby?

A The program continues normally

B The program restarts automatically

C The error is ignored silently

D The program crashes and shows an error message

Without rescue, Ruby stops the program and shows the error.

Which keyword is used to handle exceptions in Ruby?

A rescue

B try

C catch

D except

rescue is Ruby's keyword for error handling.

Can rescue handle multiple types of errors?

A No, only one error type at a time

B Yes, by specifying error classes

C Only syntax errors

D Only runtime errors

You can specify which error classes rescue should catch.

Why should you use rescue in your Ruby programs?

A To write shorter code

B To make programs run faster

C To handle errors gracefully and keep programs running

D To avoid writing comments

rescue helps programs handle errors without crashing.

Explain why Ruby uses rescue for error handling and how it helps programs.

Think about what happens when something goes wrong in a program.

Describe what would happen if you did not use rescue in a Ruby program when an error occurs.

Imagine a program breaking suddenly without warning.

Practice

1. Why do Ruby programs use rescue in error handling?

easy

A. To make the code shorter

B. To speed up the program execution

C. To catch errors and prevent the program from crashing

D. To automatically fix all errors

Solution

1. Step 1: Understand the purpose of rescue

   rescue is used to catch errors that happen during program execution.

2. Step 2: Recognize the benefit of catching errors

   Catching errors prevents the program from crashing and allows it to handle problems gracefully.

3. Final Answer:

   To catch errors and prevent the program from crashing -> Option C

4. Quick Check:

   rescue catches errors = C [OK]

Hint: Remember: rescue stops crashes by catching errors [OK]

Common Mistakes:

• Thinking rescue speeds up code
• Believing rescue fixes errors automatically
• Confusing rescue with code shortening

2. Which of the following is the correct syntax to handle errors using rescue in Ruby?

easy

A. error do
# handle error
end

B. try
# code
catch
# error handling
end

C. if error
# handle error
end

D. begin
# code
rescue
# error handling
end

Solution

1. Step 1: Identify Ruby's error handling syntax

   Ruby uses begin and rescue blocks to handle errors.

2. Step 2: Compare options to Ruby syntax

   begin # code rescue # error handling end matches Ruby's syntax exactly; others use syntax from other languages or incorrect forms.

3. Final Answer:

   begin\n # code\nrescue\n # error handling\nend -> Option D

4. Quick Check:

   Ruby uses begin-rescue-end = D [OK]

Hint: Remember Ruby uses begin and rescue keywords [OK]

Common Mistakes:

• Using try-catch like other languages
• Using if statements for error handling
• Misplacing rescue outside begin-end

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

begin
  puts 10 / 0
rescue ZeroDivisionError
  puts "Cannot divide by zero!"
end

medium

A. 0

B. Cannot divide by zero!

C. Infinity

D. Error: division by zero

Solution

1. Step 1: Identify the error raised

   Dividing 10 by 0 raises a ZeroDivisionError in Ruby.

2. Step 2: Check the rescue block handling

   The rescue block catches ZeroDivisionError and prints "Cannot divide by zero!".

3. Final Answer:

   Cannot divide by zero! -> Option B

4. Quick Check:

   ZeroDivisionError caught prints message = A [OK]

Hint: Look for error type matched in rescue block [OK]

Common Mistakes:

• Expecting program to crash with error message
• Thinking division by zero returns 0 or Infinity
• Ignoring rescue block effect

4. Find the error in this Ruby code snippet:

begin
  puts 5 + '3'
rescue
  puts "Error caught!"
end

medium

A. Adding integer and string causes a TypeError

B. The rescue block is missing the error type

C. The begin keyword is not needed

D. The puts statement is incorrect

Solution

1. Step 1: Analyze the operation inside begin block

   Adding 5 (integer) and '3' (string) causes a TypeError in Ruby.

2. Step 2: Understand rescue block behavior

   The rescue block catches the error and prints "Error caught!"; the error is due to incompatible types.

3. Final Answer:

   Adding integer and string causes a TypeError -> Option A

4. Quick Check:

   TypeError from adding int and string = A [OK]

Hint: Check data types when rescue catches errors [OK]

Common Mistakes:

• Thinking rescue must specify error type
• Believing begin is optional here
• Assuming puts causes error

5. You want to handle different errors separately in Ruby. Which code correctly uses rescue to handle ZeroDivisionError and NoMethodError differently?

begin
  # some code
rescue ZeroDivisionError
  puts "Divide by zero error"
rescue NoMethodError
  puts "Method not found error"
end

hard

A. This code correctly handles each error with separate rescue blocks

B. You cannot have multiple rescue blocks; only one is allowed

C. You must use if statements inside rescue to check error type

D. Rescue only catches StandardError, so this won't work

Solution

1. Step 1: Understand multiple rescue usage

   Ruby allows multiple rescue clauses to handle different error types separately.

2. Step 2: Verify code matches correct syntax

   The code uses separate rescue blocks for ZeroDivisionError and NoMethodError, which is valid.

3. Final Answer:

   This code correctly handles each error with separate rescue blocks -> Option A

4. Quick Check:

   Multiple rescue blocks handle errors separately = B [OK]

Hint: Use multiple rescue blocks for different errors [OK]

Common Mistakes:

• Thinking only one rescue block is allowed
• Trying to use if inside rescue instead
• Believing rescue can't catch specific errors