Try–catch block in C++ - Time & Space Complexity

Time Complexity: Try-catch block

O(n)

Understanding Time Complexity

We want to understand how using a try-catch block affects the time it takes for a program to run.

Specifically, does catching errors change how long the program works as the input grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

try {
    for (int i = 0; i < n; i++) {
        // some operation
    }
} catch (const std::exception &e) {
    std::cout << "Error caught" << std::endl;
}
    

This code tries to run a loop n times and catches any exceptions that happen.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop running n times.
• How many times: Exactly n times, once for each loop cycle.

How Execution Grows With Input

As n grows, the loop runs more times, so the work grows directly with n.

Input Size (n)	Approx. Operations
10	About 10 loop operations
100	About 100 loop operations
1000	About 1000 loop operations

Pattern observation: The work grows in a straight line as n increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows directly with the size of the input n.

Common Mistake

[X] Wrong: "The try-catch block makes the code slower for every loop cycle."

[OK] Correct: The try-catch block itself does not slow down the loop unless an exception actually happens. Normal execution runs at the same speed.

Interview Connect

Understanding how error handling affects performance helps you write reliable code without guessing about speed. This skill shows you think about both correctness and efficiency.

Self-Check

"What if the code inside the try block threw an exception every time? How would that affect the time complexity?"

Practice

1.

What is the main purpose of a try-catch block in C++?

easy

A. To handle errors and exceptions safely during program execution

B. To speed up the program by skipping code

C. To declare variables globally

D. To create loops that run multiple times

Solution

1. Step 1: Understand the role of try block

   The try block contains code that might cause an error or exception.

2. Step 2: Understand the role of catch block

   The catch block handles the error so the program does not crash.

3. Final Answer:

   To handle errors and exceptions safely during program execution -> Option A

4. Quick Check:

   Try-catch handles errors = B [OK]

Hint: Try-catch blocks catch errors to keep programs running [OK]

Common Mistakes:

• Thinking try-catch speeds up code
• Confusing try-catch with loops
• Using try-catch to declare variables

2.

Which of the following is the correct syntax to start a try block in C++?

?

easy

A. catch {

B. try (

C. try:

D. try {

Solution

1. Step 1: Recall try block syntax

   The try block starts with the keyword try followed by curly braces { }.

2. Step 2: Identify correct option

   Only try { uses try { which is correct syntax to start the block.

3. Final Answer:

   try { -> Option D

4. Quick Check:

   Try block starts with try { = C [OK]

Hint: Try block always starts with 'try {' in C++ [OK]

Common Mistakes:

• Using parentheses instead of curly braces
• Starting with catch instead of try
• Using colon after try

3.

What will be the output of the following C++ code?

try {
    int x = 5 / 0;
    std::cout << "Result: " << x << std::endl;
} catch (const std::exception& e) {
    std::cout << "Caught exception" << std::endl;
}

medium

A. Result: 0

B. Caught exception

C. Program crashes with division by zero error

D. No output

Solution

1. Step 1: Analyze division by zero in C++

   Integer division by zero causes undefined behavior and usually crashes the program; it does not throw a standard exception.

2. Step 2: Check catch block type

   The catch block catches std::exception types, but division by zero does not throw this exception automatically.

3. Final Answer:

   Program crashes with division by zero error -> Option C

4. Quick Check:

   Integer division by zero crashes = D [OK]

Hint: Division by zero crashes, not caught by std::exception [OK]

Common Mistakes:

• Assuming catch block catches all errors
• Expecting output 'Caught exception'
• Thinking division by zero returns zero

4.

Identify the error in this C++ code snippet:

try {
    throw 10;
} catch (int e) {
    std::cout << "Caught int: " << e << std::endl;
} catch (...) {
    std::cout << "Caught unknown" << std::endl;
}

medium

A. The catch block for int should come after catch(...)

B. No error; code is correct

C. Multiple catch blocks are not allowed

D. Throwing int is invalid

Solution

1. Step 1: Check throw and catch types

   The code throws an int and catches it with catch(int e), which matches correctly.

2. Step 2: Verify catch block order

   The specific catch catch(int e) comes before the catch-all catch(...), which is correct.

3. Final Answer:

   No error; code is correct -> Option B

4. Quick Check:

   Throw int caught by int catch first = A [OK]

Hint: Specific catch blocks must come before catch(...) [OK]

Common Mistakes:

• Placing catch(...) before specific catch
• Thinking multiple catch blocks are invalid
• Believing throwing int is not allowed

5.

Consider this code snippet:

try {
    std::string s = "hello";
    int n = std::stoi(s);
    std::cout << n << std::endl;
} catch (const std::invalid_argument& e) {
    std::cout << "Invalid argument caught" << std::endl;
} catch (...) {
    std::cout << "Other exception caught" << std::endl;
}

What will be the output and why?

hard

A. Invalid argument caught

B. Other exception caught

C. hello

D. Program crashes

Solution

1. Step 1: Understand std::stoi behavior

   Trying to convert "hello" to int using std::stoi throws std::invalid_argument exception because "hello" is not a number.

2. Step 2: Check catch blocks

   The first catch block catches std::invalid_argument exceptions and prints "Invalid argument caught".

3. Final Answer:

   Invalid argument caught -> Option A

4. Quick Check:

   std::stoi throws invalid_argument for non-numeric string = A [OK]

Hint: std::stoi throws invalid_argument on bad input [OK]

Common Mistakes:

• Expecting program to print 'hello'
• Assuming catch(...) runs instead of specific catch
• Thinking program crashes without catch