Custom exception classes in C Sharp (C#) - Time & Space Complexity

Time Complexity: Custom exception classes

O(1)

Understanding Time Complexity

When we create custom exception classes, we want to know how much extra work the program does when it throws or handles these exceptions.

We ask: How does the time to create and use a custom exception grow as the program runs?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

public class MyCustomException : Exception
{
    public MyCustomException(string message) : base(message) {}
}

void Process(int n)
{
    for (int i = 0; i < n; i++)
    {
        if (i == 5) throw new MyCustomException("Error at 5");
    }
}
    

This code defines a custom exception and throws it inside a loop when a condition is met.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop runs from 0 to n-1.
• How many times: Up to n times, but the exception stops the loop early at i = 5.

How Execution Grows With Input

As n grows, the loop runs more times until it hits the exception condition.

Input Size (n)	Approx. Operations
10	6 (loop stops at i=5)
100	6 (loop stops at i=5)
1000	6 (loop stops at i=5)

Pattern observation: The loop stops early, so operations stay about the same regardless of n.

Final Time Complexity

Time Complexity: O(1)

This means the time to throw the custom exception does not grow with input size because it happens at a fixed point.

Common Mistake

[X] Wrong: "Creating a custom exception always makes the program slower as input grows."

[OK] Correct: The exception is thrown at a specific point, so the time to create it does not depend on input size.

Interview Connect

Understanding how exceptions affect program speed helps you write clear and efficient error handling, a useful skill in real projects and interviews.

Self-Check

"What if the exception was thrown inside a nested loop that runs n times inside another n times? How would the time complexity change?"

Practice

1. What is the main reason to create a custom exception class in C#?

easy

A. To automatically fix errors when they occur

B. To make the program run faster

C. To avoid using try-catch blocks

D. To represent specific error conditions clearly in your program

Solution

1. Step 1: Understand the purpose of exceptions

   Exceptions represent errors or unexpected situations in a program.

2. Step 2: Identify why custom exceptions are used

   Custom exceptions help describe specific problems clearly, making error handling easier and more meaningful.

3. Final Answer:

   To represent specific error conditions clearly in your program -> Option D

4. Quick Check:

   Custom exceptions clarify errors = A [OK]

Hint: Custom exceptions explain specific errors clearly [OK]

Common Mistakes:

• Thinking custom exceptions improve speed
• Believing they remove need for try-catch
• Assuming they fix errors automatically

2. Which of the following is the correct way to declare a custom exception class named MyException in C#?

easy

A. class MyException : Exception { public MyException(string message) : base(message) {} }

B. class MyException { public MyException(string message) {} }

C. class MyException : int { public MyException(string message) : base(message) {} }

D. class MyException : Exception { public void MyException(string message) {} }

Solution

1. Step 1: Check inheritance from Exception

   Custom exceptions must inherit from Exception to behave like exceptions.

2. Step 2: Verify constructor calls base constructor

   The constructor should call base(message) to pass the error message properly.

3. Final Answer:

   class MyException : Exception { public MyException(string message) : base(message) {} } -> Option A

4. Quick Check:

   Inherit Exception + call base constructor = A [OK]

Hint: Inherit Exception and call base constructor for message [OK]

Common Mistakes:

• Not inheriting from Exception
• Using wrong base class like int
• Defining constructor as void method

3. What will be the output of the following C# code?

class MyException : Exception { public MyException(string message) : base(message) {} }
try {
  throw new MyException("Error happened");
} catch (MyException ex) {
  Console.WriteLine(ex.Message);
}

medium

A. Exception caught

B. Error happened

C. MyException

D. No output

Solution

1. Step 1: Understand the throw statement

   The code throws a MyException with message "Error happened".

2. Step 2: Catch block prints exception message

   The catch block catches MyException and prints ex.Message, which is "Error happened".

3. Final Answer:

   Error happened -> Option B

4. Quick Check:

   Throw and catch prints message = C [OK]

Hint: Catch prints exception message property [OK]

Common Mistakes:

• Expecting class name instead of message
• Thinking catch block won't run
• Assuming no output from exception

4. Identify the error in this custom exception class declaration:

class MyError : Exception {
  public MyError(string msg) {
    base(msg);
  }
}

medium

A. The class must not inherit from Exception

B. The constructor should be named differently from the class

C. The constructor should call base(msg) using a colon, not inside the body

D. The base class Exception does not accept a string parameter

Solution

1. Step 1: Check constructor syntax for base call

   In C#, calling the base class constructor must be done with a colon after the constructor signature, not inside the body.

2. Step 2: Identify correct syntax

   The correct syntax is public MyError(string msg) : base(msg) {}, not calling base(msg); inside the constructor body.

3. Final Answer:

   The constructor should call base(msg) using a colon, not inside the body -> Option C

4. Quick Check:

   Base constructor call uses colon syntax = B [OK]

Hint: Call base constructor with colon, not inside method body [OK]

Common Mistakes:

• Calling base constructor inside body instead of colon
• Not inheriting from Exception
• Misnaming constructor

5. You want to create a custom exception InvalidAgeException that should be thrown when a user's age is less than 0 or greater than 120. Which of the following code snippets correctly defines and uses this exception?

hard

A. class InvalidAgeException : Exception { public InvalidAgeException(string msg) : base(msg) {} }void CheckAge(int age) { if(age < 0 || age > 120) throw new InvalidAgeException("Age is invalid"); }

B. class InvalidAgeException { public InvalidAgeException(string msg) {} }void CheckAge(int age) { if(age < 0 || age > 120) throw new InvalidAgeException("Age is invalid"); }

C. class InvalidAgeException : Exception { public void InvalidAgeException(string msg) {} }void CheckAge(int age) { if(age < 0 || age > 120) throw new InvalidAgeException("Age is invalid"); }

D. class InvalidAgeException : Exception { public InvalidAgeException() {} }void CheckAge(int age) { if(age < 0 || age > 120) throw new InvalidAgeException(); }

Solution

1. Step 1: Verify custom exception class definition

   The class inherits from Exception and has a constructor calling base(msg) to pass the message.

2. Step 2: Check usage in method

   The method throws the exception with a message when age is invalid, which matches the requirement.

3. Final Answer:

   Correct class inheritance, constructor, and usage with message -> Option A

4. Quick Check:

   Inherit Exception + throw with message = D [OK]

Hint: Inherit Exception, add constructor, throw with message [OK]

Common Mistakes:

• Not inheriting from Exception
• Defining constructor as void method
• Missing message in exception constructor