IRB for interactive exploration in Ruby - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does IRB stand for in Ruby?

IRB stands for Interactive Ruby Shell. It lets you write and test Ruby code quickly in a command-line environment.

beginner

How do you start IRB in your terminal?

You start IRB by typing irb in your terminal and pressing Enter. This opens an interactive Ruby session.

beginner

What is the main benefit of using IRB for Ruby programming?

IRB lets you try out Ruby code instantly without creating a file. It's great for learning, testing ideas, and debugging.

beginner

How can you exit the IRB session?

You can exit IRB by typing exit or pressing Ctrl + D in the terminal.

beginner

Can you define variables and run methods inside IRB?

Yes! IRB works like a mini Ruby program where you can define variables, write methods, and see results immediately.

What command starts an IRB session?

A irb

B ruby start

C run irb

D ruby shell

Typing irb in the terminal starts the Interactive Ruby Shell.

How do you exit IRB?

A quit

B stop

C exit or Ctrl + D

D end

You can type exit or press Ctrl + D to leave IRB.

Which of these is NOT a feature of IRB?

A Create and save Ruby files automatically

B Test small code snippets quickly

C Define variables and methods interactively

D Instantly run Ruby code

IRB does not save files automatically; it is for interactive code testing only.

Why is IRB useful for beginners?

A It compiles Ruby code into machine language

B It lets you try Ruby code without writing a full program

C It creates graphical user interfaces

D It manages Ruby project dependencies

IRB allows beginners to experiment with Ruby code quickly and easily.

What happens when you type Ruby code in IRB?

A The code is saved to a file

B The code is ignored

C The code is sent to a server

D The code runs immediately and shows the result

IRB runs your Ruby code instantly and displays the output right away.

Explain what IRB is and how it helps when learning Ruby.

Think about how you can try code without making a file.

Describe the steps to start and exit an IRB session.

Focus on the commands you type in the terminal.

Practice

1. What is the main purpose of using irb in Ruby?

easy

A. To debug Ruby code with a graphical interface

B. To run Ruby code interactively and test snippets quickly

C. To create Ruby project files automatically

D. To compile Ruby code into an executable file

Solution

1. Step 1: Understand what IRB stands for

   IRB means Interactive Ruby Shell, which lets you type and run Ruby code line by line.

2. Step 2: Identify the main use of IRB

   It is mainly used to quickly test and explore Ruby code without creating files.

3. Final Answer:

   To run Ruby code interactively and test snippets quickly -> Option B

4. Quick Check:

   IRB = Interactive Ruby Shell for quick code testing [OK]

Hint: IRB runs code live, no files needed [OK]

Common Mistakes:

• Thinking IRB compiles code
• Confusing IRB with project setup tools
• Assuming IRB has a graphical interface

2. Which command correctly starts the IRB session in your terminal?

easy

A. ruby irb

B. start irb

C. run ruby

D. irb

Solution

1. Step 1: Recall the command to launch IRB

   The IRB session is started simply by typing irb in the terminal.

2. Step 2: Check other options for correctness

   Commands like ruby irb, start irb, or run ruby are incorrect for starting IRB.

3. Final Answer:

   irb -> Option D

4. Quick Check:

   Type irb to start IRB [OK]

Hint: Just type 'irb' to start interactive Ruby [OK]

Common Mistakes:

• Adding extra words like 'ruby' before irb
• Using 'start' or 'run' commands incorrectly
• Confusing IRB start with running Ruby files

3. What will be the output when you enter this in IRB?

5.times { |i| puts i }

medium

A. 5 times printed on one line

B. 1 2 3 4 5 (each on a new line)

C. 0 1 2 3 4 (each on a new line)

D. Error: undefined method 'times'

Solution

1. Step 1: Understand the times method

   The times method runs the block 5 times, with i from 0 to 4.

2. Step 2: Check what puts i does inside the block

   It prints each value of i on a new line, so output is 0,1,2,3,4 each on separate lines.

3. Final Answer:

   0 1 2 3 4 (each on a new line) -> Option C

4. Quick Check:

   5.times counts from 0 to 4 [OK]

Hint: times starts counting from zero [OK]

Common Mistakes:

• Thinking times starts at 1
• Expecting output on one line
• Assuming times is undefined in IRB

4. You typed this in IRB:

puts 'Hello

What is the error and how do you fix it?

medium

A. SyntaxError due to missing closing quote; add a closing '

B. NameError because 'Hello' is undefined; define it first

C. No error; it prints Hello

D. RuntimeError because puts is not allowed in IRB

Solution

1. Step 1: Identify the syntax problem

   The string started with a single quote but has no closing quote, causing a SyntaxError.

2. Step 2: Fix the error by adding the missing quote

   Adding the closing single quote after Hello fixes the syntax and allows the code to run.

3. Final Answer:

   SyntaxError due to missing closing quote; add a closing ' -> Option A

4. Quick Check:

   Strings need matching quotes [OK]

Hint: Check for matching quotes in strings [OK]

Common Mistakes:

• Ignoring missing quote errors
• Thinking puts can't be used in IRB
• Confusing SyntaxError with NameError

5. You want to quickly test a method in IRB that returns the square of a number. Which of these is the correct way to define and test it?

hard

A. def square(x); x * x; end; square(4)

B. def square x x * x end square 4

C. def square(x) { return x * x }; square(4)

D. def square(x): return x * x end; square(4)

Solution

1. Step 1: Check correct Ruby method syntax

   Ruby methods use def name(params); body; end syntax. def square(x); x * x; end; square(4) follows this correctly.

2. Step 2: Verify method call syntax

   Calling square(4) is correct. The other options have syntax errors or wrong Ruby style.

3. Final Answer:

   def square(x); x * x; end; square(4) -> Option A

4. Quick Check:

   Method def/end with parentheses is correct [OK]

Hint: Use def ... end with parentheses for methods [OK]

Common Mistakes:

• Using braces {} for method body
• Omitting parentheses incorrectly
• Using Python-like syntax with colons