Begin/rescue/end blocks in Ruby - Step-by-Step Execution

Concept Flow - Begin/rescue/end blocks

Start begin block

↓

Execute code inside begin

↓

Error?

No→End begin block

Yes↓

Enter rescue block

↓

Handle error

↓

End begin block

The program tries code inside begin. If an error happens, it jumps to rescue to handle it, then ends the block.

Execution Sample

Ruby

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

Tries to divide 10 by x; if x is zero, rescue prints a message instead of crashing.

Execution Table

Step	Action	Code Line	Result	Output
1	Start begin block	begin	Begin block started
2	Execute division	puts 10 / x	Error: undefined local variable or method `x'
3	Error caught	rescue ZeroDivisionError	No ZeroDivisionError, but NameError raised
4	Unhandled error	end	Program crashes with NameError

💡 Execution stops due to unhandled NameError because x is not defined

Variable Tracker

Variable	Start	After Step 2	Final
x	undefined	undefined	undefined

Key Moments - 2 Insights

Why does the rescue block not catch the error in step 2?

Because the error is NameError (undefined variable), but rescue only catches ZeroDivisionError as shown in execution_table row 3.

What happens if the error matches the rescue type?

The program jumps to the rescue block to run its code, then continues after end, preventing a crash.

Visual Quiz - 3 Questions

Look at the execution table, what error occurs at step 2?

A No error

B ZeroDivisionError

C NameError

D SyntaxError

💡 Hint

Check the 'Result' column in step 2 of the execution_table

At which step does the program crash due to unhandled error?

A Step 4

B Step 1

C Step 3

D Step 2

💡 Hint

Look at the 'Result' column for step 4 in execution_table

If x was zero, which step would rescue handle the error?

A Step 2

B Step 3

C Step 4

D Step 1

💡 Hint

Rescue handles ZeroDivisionError as shown in step 3 of execution_table

Concept Snapshot

begin
  # code that might fail
rescue ErrorType
  # code to handle error
end

- begin runs code
- rescue catches errors of given type
- end closes block
- prevents program crash by handling errors

Full Transcript

This example shows how Ruby's begin/rescue/end blocks work. The program tries to run code inside begin. If an error happens, it looks for a matching rescue block to handle it. If the error matches, rescue runs its code to fix or report the problem, then the program continues safely. If no rescue matches, the program crashes. In the example, dividing by x causes an error. Since x is not defined, a NameError happens, but rescue only catches ZeroDivisionError, so the program crashes. If x was zero, rescue would catch the division error and print a message instead of crashing.

Practice

1. What is the purpose of the begin/rescue/end block in Ruby?

easy

A. To declare variables

B. To create a loop that repeats code

C. To define a new method

D. To handle errors and prevent the program from crashing

Solution

1. Step 1: Understand the role of begin block

   The begin block contains code that might cause an error.

2. Step 2: Understand the role of rescue block

   The rescue block catches errors and handles them so the program doesn't crash.

3. Final Answer:

   To handle errors and prevent the program from crashing -> Option D

4. Quick Check:

   begin/rescue = error handling [OK]

Hint: Remember: begin/rescue is for catching errors safely [OK]

Common Mistakes:

• Thinking begin/rescue creates loops
• Confusing rescue with method definition
• Using begin/rescue to declare variables

2. Which of the following is the correct syntax to handle exceptions using begin/rescue/end in Ruby?

easy

A. begin
risky_code
rescue
handle_error
end

B. try {
risky_code
} catch {
handle_error
}

C. if error then
handle_error
end

D. begin:
risky_code
except:
handle_error

Solution

1. Step 1: Identify Ruby syntax for error handling

   Ruby uses begin, rescue, and end keywords for exceptions.

2. Step 2: Compare options with Ruby syntax

   begin risky_code rescue handle_error end matches Ruby syntax exactly; others use syntax from other languages or incorrect keywords.

3. Final Answer:

   begin\n risky_code\nrescue\n handle_error\nend -> Option A

4. Quick Check:

   Ruby error handling = begin/rescue/end [OK]

Hint: Look for Ruby keywords: begin, rescue, end [OK]

Common Mistakes:

• Using try/catch like other languages
• Using if/else for error handling
• Mixing Python or JavaScript syntax

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

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

medium

A. Cannot divide by zero

B. 0

C. 10

D. ZeroDivisionError

Solution

1. Step 1: Identify the error in the code

   The code tries to divide 10 by 0, which raises a ZeroDivisionError.

2. Step 2: Understand the rescue block

   The rescue block catches ZeroDivisionError and prints "Cannot divide by zero" instead of crashing.

3. Final Answer:

   Cannot divide by zero -> Option A

4. Quick Check:

   ZeroDivisionError caught = message printed [OK]

Hint: Divide by zero triggers rescue message [OK]

Common Mistakes:

• Expecting program to crash
• Thinking it prints 0 or 10
• Confusing error name with output

4. Find the error in this Ruby code snippet:

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

medium

A. The begin block should be replaced with try

B. The rescue block is missing the error type

C. You cannot add a number and a string directly

D. The code will run without errors

Solution

1. Step 1: Analyze the operation inside begin block

   Adding 5 (number) and "3" (string) causes a TypeError in Ruby.

2. Step 2: Check error handling

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

3. Final Answer:

   You cannot add a number and a string directly -> Option C

4. Quick Check:

   Type mismatch causes error caught [OK]

Hint: Check data types before adding values [OK]

Common Mistakes:

• Thinking rescue needs error type always
• Assuming code runs without error
• Confusing begin with try

5. How can you modify this code to handle multiple specific errors separately?

begin
  # risky code
rescue
  puts "An error occurred"
end

hard

A. Use if statements inside begin block

B. Use multiple rescue clauses with specific error classes

C. Replace rescue with else to catch errors

D. Put all code inside rescue block

Solution

1. Step 1: Understand handling multiple errors

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

2. Step 2: Apply multiple rescue clauses

   Write rescue clauses like rescue ZeroDivisionError and rescue IOError to handle errors distinctly.

3. Final Answer:

   Use multiple rescue clauses with specific error classes -> Option B

4. Quick Check:

   Multiple rescue = specific error handling [OK]

Hint: Use separate rescue for each error type [OK]

Common Mistakes:

• Using else instead of rescue
• Trying to catch errors with if statements
• Putting code inside rescue block